Techniques for managing display usage

ABSTRACT

The present disclosure generally relates managing display usage. In some embodiments, a device modifies various aspects of a displayed user interface as the device transitions from operating in a first device mode to operating in a second device mode. In some embodiments, the modifications involve altering the content included in a user interface and varying how the content is displayed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to of U.S. Provisional Application No.62/897,959, filed Sep. 9, 2019, entitled “TECHNIQUES FOR MANAGINGDISPLAY USAGE,” the entire contents of which are hereby incorporated byreference.

FIELD

The present disclosure relates generally to user interfaces, and morespecifically to techniques for displaying user interfaces with manageddisplay usage.

BACKGROUND

Electronic devices may include screens for displaying user interfaces.Over time, non-uniform use of screens may lead to discoloration ofportions of the screen and decreased quality of displayed images.

BRIEF SUMMARY

Some techniques for displaying user interfaces using electronic devices,however, are generally cumbersome and inefficient. For example, someexisting techniques use a complex and time-consuming user interface,which may include multiple key presses or keystrokes. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces with managed displayusage. Such methods and interfaces optionally complement or replaceother methods for managing display usage. Such methods improve imagequality (e.g., reduce deterioration of image quality) of displayed userinterfaces as an electronic device ages and improve the durability ofdisplay devices used to display user interfaces. In addition, suchmethods and interfaces also reduce the cognitive burden on a user andproduce a more efficient human-machine interface. For battery-operatedcomputing devices, such methods and interfaces conserve power andincrease the time between battery charges. Furthermore, such methods andinterfaces also reduce the number of unnecessary, extraneous, orrepetitive input required at computing devices, such as smartphones andsmartwatches.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: while theelectronic device is in a first mode, displaying on the display, a firstuser interface including: a first time indicator, displayed at a firstbrightness level; and a first graphical object, displayed at a secondbrightness level; detecting that the electronic device has met criteriafor transitioning from the first mode to a second mode; and in responseto detecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; while theelectronic device is in the second mode, displaying on the display, asecond user interface including: a second time indicator indicating thecurrent time, wherein the second time indicator is displayed at a thirdbrightness level that is lower than the first brightness level, at whichthe first time indicator was previously displayed, by a first amount;and a second graphical object corresponding to the first graphicalobject, wherein the second graphical object is displayed at a fourthbrightness level that is lower than the second brightness level, atwhich the first graphical object was previously displayed, by a secondamount that is different from the first amount of difference inbrightness between the first brightness level and the second brightnesslevel.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: while the electronic deviceis in a first mode, displaying on the display, a first user interfaceincluding: a first time indicator, displayed at a first brightnesslevel; and a first graphical object, displayed at a second brightnesslevel; detecting that the electronic device has met criteria fortransitioning from the first mode to a second mode; and in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; while theelectronic device is in the second mode, displaying on the display, asecond user interface including: a second time indicator indicating thecurrent time, wherein the second time indicator is displayed at a thirdbrightness level that is lower than the first brightness level, at whichthe first time indicator was previously displayed, by a first amount;and a second graphical object corresponding to the first graphicalobject, wherein the second graphical object is displayed at a fourthbrightness level that is lower than the second brightness level, atwhich the first graphical object was previously displayed, by a secondamount that is different from the first amount of difference inbrightness between the first brightness level and the second brightnesslevel.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stories one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: while the electronic device is in afirst mode, displaying on the display, a first user interface including:a first time indicator, displayed at a first brightness level; and afirst graphical object, displayed at a second brightness level;detecting that the electronic device has met criteria for transitioningfrom the first mode to a second mode; and in response to detecting thatthe electronic device has met the criteria for transitioning from thefirst mode to the second mode, transitioning the electronic device fromthe first mode to the second mode; while the electronic device is in thesecond mode, displaying on the display, a second user interfaceincluding: a second time indicator indicating the current time, whereinthe second time indicator is displayed at a third brightness level thatis lower than the first brightness level, at which the first timeindicator was previously displayed, by a first amount; and a secondgraphical object corresponding to the first graphical object, whereinthe second graphical object is displayed at a fourth brightness levelthat is lower than the second brightness level, at which the firstgraphical object was previously displayed, by a second amount that isdifferent from the first amount of difference in brightness between thefirst brightness level and the second brightness level.

In accordance with some embodiments, an electronic device is described.The electronic device comprising a display; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:while the electronic device is in a first mode, displaying on thedisplay, a first user interface including: a first time indicator,displayed at a first brightness level; and a first graphical object,displayed at a second brightness level; detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and in response to detecting that the electronic device hasmet the criteria for transitioning from the first mode to the secondmode, transitioning the electronic device from the first mode to thesecond mode; while the electronic device is in the second mode,displaying on the display, a second user interface including: a secondtime indicator indicating the current time, wherein the second timeindicator is displayed at a third brightness level that is lower thanthe first brightness level, at which the first time indicator waspreviously displayed, by a first amount; and a second graphical objectcorresponding to the first graphical object, wherein the secondgraphical object is displayed at a fourth brightness level that is lowerthan the second brightness level, at which the first graphical objectwas previously displayed, by a second amount that is different from thefirst amount of difference in brightness between the first brightnesslevel and the second brightness level.

In accordance with some embodiments, an electronic device is described.The electronic device comprising, comprising: a display; means, whilethe electronic device is in a first mode, for displaying on the display,a first user interface including: a first time indicator, displayed at afirst brightness level; and a first graphical object, displayed at asecond brightness level; means for detecting that the electronic devicehas met criteria for transitioning from the first mode to a second mode;and means, responsive to detecting that the electronic device has metthe criteria for transitioning from the first mode to the second mode,for transitioning the electronic device from the first mode to thesecond mode; means, while the electronic device is in the second mode,for displaying on the display, a second user interface including: asecond time indicator indicating the current time, wherein the secondtime indicator is displayed at a third brightness level that is lowerthan the first brightness level, at which the first time indicator waspreviously displayed, by a first amount; and a second graphical objectcorresponding to the first graphical object, wherein the secondgraphical object is displayed at a fourth brightness level that is lowerthan the second brightness level, at which the first graphical objectwas previously displayed, by a second amount that is different from thefirst amount of difference in brightness between the first brightnesslevel and the second brightness level.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: while theelectronic device is in a first mode, displaying on the display, a firstuser interface including: a first time indicator indicating a currenttime and is displayed at a first size; and a first graphical object andis displayed at a second size; and detecting that the electronic devicehas met criteria for transitioning from the first mode to a second mode;and in response to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode,transitioning the electronic device from the first mode to the secondmode; while the electronic device is in the second mode, displaying onthe display, a second user interface including: a second time indicatorindicating the current time, wherein the second time indicator isdisplayed at a third size that is smaller than the first size, at whichthe first time indicator was previously displayed; and a secondgraphical object corresponding to the first graphical object, whereinthe second graphical object is displayed at a fourth size that issmaller than the second size, at which the first graphical object waspreviously displayed.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: while the electronic deviceis in a first mode, displaying on the display, a first user interfaceincluding: a first time indicator indicating a current time and isdisplayed at a first size; and a first graphical object and is displayedat a second size; and detecting that the electronic device has metcriteria for transitioning from the first mode to a second mode; and inresponse to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, transitioningthe electronic device from the first mode to the second mode, including:while the electronic device is in the second mode, displaying on thedisplay, a second user interface including: a second time indicatorindicating the current time, wherein the second time indicator isdisplayed at a third size that is smaller than the first size, at whichthe first time indicator was previously displayed; and a secondgraphical object corresponding to the first graphical object, whereinthe second graphical object is displayed at a fourth size that issmaller than the second size, at which the first graphical object waspreviously displayed.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: while the electronic device is in afirst mode, displaying on the display, a first user interface including:a first time indicator indicating a current time and is displayed at afirst size; and a first graphical object and is displayed at a secondsize; and detecting that the electronic device has met criteria fortransitioning from the first mode to a second mode; and in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode, including:while the electronic device is in the second mode, displaying on thedisplay, a second user interface including: a second time indicatorindicating the current time, wherein the second time indicator isdisplayed at a third size that is smaller than the first size, at whichthe first time indicator was previously displayed; and a secondgraphical object corresponding to the first graphical object, whereinthe second graphical object is displayed at a fourth size that issmaller than the second size, at which the first graphical object waspreviously displayed.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:while the electronic device is in a first mode, displaying on thedisplay, a first user interface including: a first time indicatorindicating a current time and is displayed at a first size; and a firstgraphical object and is displayed at a second size; and detecting thatthe electronic device has met criteria for transitioning from the firstmode to a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, transitioning the electronic device from the first mode tothe second mode, including: while the electronic device is in the secondmode, displaying on the display, a second user interface including: asecond time indicator indicating the current time, wherein the secondtime indicator is displayed at a third size that is smaller than thefirst size, at which the first time indicator was previously displayed;and a second graphical object corresponding to the first graphicalobject, wherein the second graphical object is displayed at a fourthsize that is smaller than the second size, at which the first graphicalobject was previously displayed.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; means, while the electronicdevice is in a first mode, for displaying on the display, a first userinterface including: a first time indicator indicating a current timeand is displayed at a first size; and a first graphical object and isdisplayed at a second size; and means for detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and means, responsive to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, for transitioning the electronic device from the first modeto the second mode, including: means, while the electronic device is inthe second mode, for displaying on the display, a second user interfaceincluding: a second time indicator indicating the current time, whereinthe second time indicator is displayed at a third size that is smallerthan the first size, at which the first time indicator was previouslydisplayed; and a second graphical object corresponding to the firstgraphical object, wherein the second graphical object is displayed at afourth size that is smaller than the second size, at which the firstgraphical object was previously displayed.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display and one or moresensors: while the electronic device is in a first mode, displaying onthe display, a first user interface at a first display brightness level,the first user interface including: a first time indicator; and a firstgraphical object; receiving data from the one or more sensors; detectingthat the electronic device has met criteria for transitioning from thefirst mode to a second mode; and in response to detecting that theelectronic device has met the criteria for transitioning from the firstmode to the second mode, transitioning the electronic device from thefirst mode to the second mode; and while the electronic device is in thesecond mode: in accordance with a determination that the data from theone or more sensors corresponds to a first environmental brightnesslevel, displaying a second user interface at a second display brightnesslevel less than the first display brightness level, the second userinterface including: a second time indicator different from the firsttime indicator in one or more visual characteristics other thanbrightness; and a second graphical object that corresponds to the firstgraphical object; in accordance with a determination that the data fromthe one or more sensors corresponds to a second environmental brightnesslevel lower than the first environmental brightness level, displaying athird user interface user interface at a third display brightness levellower than the second display brightness level, the third user interfaceincluding different content than the second user interface.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display and one ormore sensors, the one or more programs including instructions for: whilethe electronic device is in a first mode, displaying on the display, afirst user interface at a first display brightness level, the first userinterface including: a first time indicator; and a first graphicalobject; receiving data from the one or more sensors; detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, transitioning the electronic device from the first mode tothe second mode; and while the electronic device is in the second mode:in accordance with a determination that the data from the one or moresensors corresponds to a first environmental brightness level,displaying a second user interface at a second display brightness levelless than the first display brightness level, the second user interfaceincluding: a second time indicator different from the first timeindicator in one or more visual characteristics other than brightness;and a second graphical object that corresponds to the first graphicalobject; in accordance with a determination that the data from the one ormore sensors corresponds to a second environmental brightness levellower than the first environmental brightness level, displaying a thirduser interface user interface at a third display brightness level lowerthan the second display brightness level, the third user interfaceincluding different content than the second user interface.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display and one or moresensors, the one or more programs including instructions for: while theelectronic device is in a first mode, displaying on the display, a firstuser interface at a first display brightness level, the first userinterface including: a first time indicator; and a first graphicalobject; receiving data from the one or more sensors; detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, transitioning the electronic device from the first mode tothe second mode; and while the electronic device is in the second mode:in accordance with a determination that the data from the one or moresensors corresponds to a first environmental brightness level,displaying a second user interface at a second display brightness levelless than the first display brightness level, the second user interfaceincluding: a second time indicator different from the first timeindicator in one or more visual characteristics other than brightness;and a second graphical object that corresponds to the first graphicalobject; in accordance with a determination that the data from the one ormore sensors corresponds to a second environmental brightness levellower than the first environmental brightness level, displaying a thirduser interface user interface at a third display brightness level lowerthan the second display brightness level, the third user interfaceincluding different content than the second user interface.

In accordance with some embodiments, an electronic device is described.The electronic device, comprising: a display; one or more sensors; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: while the electronic device is in a firstmode, displaying on the display, a first user interface at a firstdisplay brightness level, the first user interface including: a firsttime indicator; and a first graphical object; receiving data from theone or more sensors; detecting that the electronic device has metcriteria for transitioning from the first mode to a second mode; and inresponse to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, transitioningthe electronic device from the first mode to the second mode; and whilethe electronic device is in the second mode: in accordance with adetermination that the data from the one or more sensors corresponds toa first environmental brightness level, displaying a second userinterface at a second display brightness level less than the firstdisplay brightness level, the second user interface including: a secondtime indicator different from the first time indicator in one or morevisual characteristics other than brightness; and a second graphicalobject that corresponds to the first graphical object; in accordancewith a determination that the data from the one or more sensorscorresponds to a second environmental brightness level lower than thefirst environmental brightness level, displaying a third user interfaceuser interface at a third display brightness level lower than the seconddisplay brightness level, the third user interface including differentcontent than the second user interface.

In accordance with some embodiments, an electronic device is described.The electronic device, comprising: a display; one or more sensors;means, while the electronic device is in a first mode, for displaying onthe display, a first user interface at a first display brightness level,the first user interface including: a first time indicator; and a firstgraphical object; means for receiving data from the one or more sensors;means for detecting that the electronic device has met criteria fortransitioning from the first mode to a second mode; and means,responsive to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, fortransitioning the electronic device from the first mode to the secondmode; and means, while the electronic device is in the second mode, for:in accordance with a determination that the data from the one or moresensors corresponds to a first environmental brightness level,displaying a second user interface at a second display brightness levelless than the first display brightness level, the second user interfaceincluding: a second time indicator different from the first timeindicator in one or more visual characteristics other than brightness;and a second graphical object that corresponds to the first graphicalobject; in accordance with a determination that the data from the one ormore sensors corresponds to a second environmental brightness levellower than the first environmental brightness level, displaying a thirduser interface user interface at a third display brightness level lowerthan the second display brightness level, the third user interfaceincluding different content than the second user interface.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: displaying a userinterface that includes a plurality of user interface elements includinga graphical representation of a first type of information that isassociated with a first application; while the electronic device is in afirst mode: updating the appearance of the graphical representation ofthe first type of information over time with a first update interval;and after updating the appearance of the graphical representation of thefirst type of information over time one or more times at the firstupdate interval, detecting that the electronic device has met criteriafor transitioning from the first mode to a second mode; in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; and while theelectronic device is in the second mode, updating the appearance of thegraphical representation of the first type of information over time witha second update interval that is different from the first updateinterval.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: displaying a user interfacethat includes a plurality of user interface elements including agraphical representation of a first type of information that isassociated with a first application; while the electronic device is in afirst mode: updating the appearance of the graphical representation ofthe first type of information over time with a first update interval;and after updating the appearance of the graphical representation of thefirst type of information over time one or more times at the firstupdate interval, detecting that the electronic device has met criteriafor transitioning from the first mode to a second mode; in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; and while theelectronic device is in the second mode, updating the appearance of thegraphical representation of the first type of information over time witha second update interval that is different from the first updateinterval.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: displaying a user interface thatincludes a plurality of user interface elements including a graphicalrepresentation of a first type of information that is associated with afirst application; while the electronic device is in a first mode:updating the appearance of the graphical representation of the firsttype of information over time with a first update interval; and afterupdating the appearance of the graphical representation of the firsttype of information over time one or more times at the first updateinterval, detecting that the electronic device has met criteria fortransitioning from the first mode to a second mode; in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; and while theelectronic device is in the second mode, updating the appearance of thegraphical representation of the first type of information over time witha second update interval that is different from the first updateinterval.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:displaying a user interface that includes a plurality of user interfaceelements including a graphical representation of a first type ofinformation that is associated with a first application; while theelectronic device is in a first mode: updating the appearance of thegraphical representation of the first type of information over time witha first update interval; and after updating the appearance of thegraphical representation of the first type of information over time oneor more times at the first update interval, detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode; in response to detecting that the electronic devicehas met the criteria for transitioning from the first mode to the secondmode, transitioning the electronic device from the first mode to thesecond mode; and while the electronic device is in the second mode,updating the appearance of the graphical representation of the firsttype of information over time with a second update interval that isdifferent from the first update interval.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; means for displaying a userinterface that includes a plurality of user interface elements includinga graphical representation of a first type of information that isassociated with a first application; means, while the electronic deviceis in a first mode, for: updating the appearance of the graphicalrepresentation of the first type of information over time with a firstupdate interval; and after updating the appearance of the graphicalrepresentation of the first type of information over time one or moretimes at the first update interval, detecting that the electronic devicehas met criteria for transitioning from the first mode to a second mode;means, responsive to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode, fortransitioning the electronic device from the first mode to the secondmode; and means, while the electronic device is in the second mode, forupdating the appearance of the graphical representation of the firsttype of information over time with a second update interval that isdifferent from the first update interval.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: while theelectronic device is operating in a first mode, displaying, on thedisplay, a first user interface of a first application, the first userinterface including a first graphical object corresponding to the firstapplication; while displaying the first user interface, detecting thatthe electronic device has met criteria for transitioning from the firstmode to a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode: in accordance with a determination that the firstapplication is an application of a first type, replacing display of thefirst user interface of the first application with a second userinterface of the first application different from the first userinterface, the second user interface including a second graphical objectcorresponding to the first application; in accordance with adetermination that the first application is an application of a secondtype, replacing display of the first user interface of the firstapplication with a third user interface different from the first userinterface of the first application and the second user interface of thefirst application, the third user interface that is an operating systemuser interface including one or more elements that are not part of thefirst user interface of the first application, including a timeindicator.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: while the electronic deviceis operating in a first mode, displaying, on the display, a first userinterface of a first application, the first user interface including afirst graphical object corresponding to the first application; whiledisplaying the first user interface, detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and in response to detecting that the electronic device hasmet the criteria for transitioning from the first mode to the secondmode: in accordance with a determination that the first application isan application of a first type, replacing display of the first userinterface of the first application with a second user interface of thefirst application different from the first user interface, the seconduser interface including a second graphical object corresponding to thefirst application; in accordance with a determination that the firstapplication is an application of a second type, replacing display of thefirst user interface of the first application with a third userinterface different from the first user interface of the firstapplication and the second user interface of the first application, thethird user interface that is an operating system user interfaceincluding one or more elements that are not part of the first userinterface of the first application, including a time indicator.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: while the electronic device isoperating in a first mode, displaying, on the display, a first userinterface of a first application, the first user interface including afirst graphical object corresponding to the first application; whiledisplaying the first user interface, detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and in response to detecting that the electronic device hasmet the criteria for transitioning from the first mode to the secondmode: in accordance with a determination that the first application isan application of a first type, replacing display of the first userinterface of the first application with a second user interface of thefirst application different from the first user interface, the seconduser interface including a second graphical object corresponding to thefirst application; in accordance with a determination that the firstapplication is an application of a second type, replacing display of thefirst user interface of the first application with a third userinterface different from the first user interface of the firstapplication and the second user interface of the first application, thethird user interface that is an operating system user interfaceincluding one or more elements that are not part of the first userinterface of the first application, including a time indicator.

In accordance with some embodiments, an electronic device, comprising: adisplay; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: while the electronic device isoperating in a first mode, displaying, on the display, a first userinterface of a first application, the first user interface including afirst graphical object corresponding to the first application; whiledisplaying the first user interface, detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and in response to detecting that the electronic device hasmet the criteria for transitioning from the first mode to the secondmode: in accordance with a determination that the first application isan application of a first type, replacing display of the first userinterface of the first application with a second user interface of thefirst application different from the first user interface, the seconduser interface including a second graphical object corresponding to thefirst application; in accordance with a determination that the firstapplication is an application of a second type, replacing display of thefirst user interface of the first application with a third userinterface different from the first user interface of the firstapplication and the second user interface of the first application, thethird user interface that is an operating system user interfaceincluding one or more elements that are not part of the first userinterface of the first application, including a time indicator.

In accordance with some embodiments, an electronic device, comprising: adisplay; means, while the electronic device is operating in a firstmode, for displaying, on the display, a first user interface of a firstapplication, the first user interface including a first graphical objectcorresponding to the first application; means, while displaying thefirst user interface, for detecting that the electronic device has metcriteria for transitioning from the first mode to a second mode; andmeans, responsive to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode, for:in accordance with a determination that the first application is anapplication of a first type, replacing display of the first userinterface of the first application with a second user interface of thefirst application different from the first user interface, the seconduser interface including a second graphical object corresponding to thefirst application; in accordance with a determination that the firstapplication is an application of a second type, replacing display of thefirst user interface of the first application with a third userinterface different from the first user interface of the firstapplication and the second user interface of the first application, thethird user interface that is an operating system user interfaceincluding one or more elements that are not part of the first userinterface of the first application, including a time indicator.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: while theelectronic device is operating in a first mode: displaying, on thedisplay, a first user interface of a first application with anarrangement of user interface elements determined by the firstapplication; and displaying, on the display, a second user interface ofa second application with an arrangement of user interface elementsdetermined by the second application; while the electronic device isoperating in the first mode, detecting that the electronic device hasmet criteria for transitioning from the first mode to a second mode; andin response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, transitioningfrom the first mode to the second mode, including: in accordance with adetermination that the first application was displayed on the displaywhen the electronic device detected that the electronic device has metcriteria for transitioning from the first mode to a second mode,displaying information from the first application in a predefinedtemplate; and in accordance with a determination that the secondapplication was displayed on the display when the electronic devicedetected that the electronic device has met criteria for transitioningfrom the first mode to a second mode, displaying information from thesecond application in the predefined template.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: while the electronic deviceis operating in a first mode: displaying, on the display, a first userinterface of a first application with an arrangement of user interfaceelements determined by the first application; and displaying, on thedisplay, a second user interface of a second application with anarrangement of user interface elements determined by the secondapplication; while the electronic device is operating in the first mode,detecting that the electronic device has met criteria for transitioningfrom the first mode to a second mode; and in response to detecting thatthe electronic device has met the criteria for transitioning from thefirst mode to the second mode, transitioning from the first mode to thesecond mode, including: in accordance with a determination that thefirst application was displayed on the display when the electronicdevice detected that the electronic device has met criteria fortransitioning from the first mode to a second mode displayinginformation from the first application in a predefined template; and inaccordance with a determination that the second application wasdisplayed on the display when the electronic device detected that theelectronic device has met criteria for transitioning from the first modeto a second mode, displaying information from the second application inthe predefined template.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: while the electronic device isoperating in a first mode: displaying, on the display, a first userinterface of a first application with an arrangement of user interfaceelements determined by the first application; and displaying, on thedisplay, a second user interface of a second application with anarrangement of user interface elements determined by the secondapplication; while the electronic device is operating in the first mode,detecting that the electronic device has met criteria for transitioningfrom the first mode to a second mode; and in response to detecting thatthe electronic device has met the criteria for transitioning from thefirst mode to the second mode, transitioning from the first mode to thesecond mode, including: in accordance with a determination that thefirst application was displayed on the display when the electronicdevice detected that the electronic device has met criteria fortransitioning from the first mode to a second mode displayinginformation from the first application in a predefined template; and inaccordance with a determination that the second application wasdisplayed on the display when the electronic device detected that theelectronic device has met criteria for transitioning from the first modeto a second mode, displaying information from the second application inthe predefined template.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:while the electronic device is operating in a first mode: displaying, onthe display, a first user interface of a first application with anarrangement of user interface elements determined by the firstapplication; and displaying, on the display, a second user interface ofa second application with an arrangement of user interface elementsdetermined by the second application; while the electronic device isoperating in the first mode, detecting that the electronic device hasmet criteria for transitioning from the first mode to a second mode; andin response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, transitioningfrom the first mode to the second mode, including: in accordance with adetermination that the first application was displayed on the displaywhen the electronic device detected that the electronic device has metcriteria for transitioning from the first mode to a second modedisplaying information from the first application in a predefinedtemplate; and in accordance with a determination that the secondapplication was displayed on the display when the electronic devicedetected that the electronic device has met criteria for transitioningfrom the first mode to a second mode, displaying information from thesecond application in the predefined template.

In accordance with some embodiments, an electronic device is described.The electronic device comprising: a display; means, while the electronicdevice is operating in a first mode, for: displaying, on the display, afirst user interface of a first application with an arrangement of userinterface elements determined by the first application; and displaying,on the display, a second user interface of a second application with anarrangement of user interface elements determined by the secondapplication; means, while the electronic device is operating in thefirst mode, for detecting that the electronic device has met criteriafor transitioning from the first mode to a second mode; and means,responsive to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, fortransitioning from the first mode to the second mode, including: inaccordance with a determination that the first application was displayedon the display when the electronic device detected that the electronicdevice has met criteria for transitioning from the first mode to asecond mode displaying information from the first application in apredefined template; and in accordance with a determination that thesecond application was displayed on the display when the electronicdevice detected that the electronic device has met criteria fortransitioning from the first mode to a second mode, displayinginformation from the second application in the predefined template.

In accordance with some embodiments, a method is described. The methodcomprises: at an electronic device having a display: while theelectronic device is operating in a first mode, displaying, on thedisplay, a first user interface of an application; detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode: transitioning from the first mode to the second mode;replacing, on the display, the first user interface with a second userinterface including an obscured representation of at least a portion ofthe first user interface of the application; and displaying a timeindicator at a position on the display overlapping at least a portion ofthe obscured representation of the at least a portion of the first userinterface of the application.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, the oneor more programs including instructions for: while the electronic deviceis operating in a first mode, displaying, on the display, a first userinterface of an application; detecting that the electronic device hasmet criteria for transitioning from the first mode to a second mode; andin response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode: transitioningfrom the first mode to the second mode; replacing, on the display, thefirst user interface with a second user interface including an obscuredrepresentation of at least a portion of the first user interface of theapplication; and displaying a time indicator at a position on thedisplay overlapping at least a portion of the obscured representation ofthe at least a portion of the first user interface of the application.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: while the electronic device isoperating in a first mode, displaying, on the display, a first userinterface of an application; detecting that the electronic device hasmet criteria for transitioning from the first mode to a second mode; andin response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode: transitioningfrom the first mode to the second mode; replacing, on the display, thefirst user interface with a second user interface including an obscuredrepresentation of at least a portion of the first user interface of theapplication; and displaying a time indicator at a position on thedisplay overlapping at least a portion of the obscured representation ofthe at least a portion of the first user interface of the application.

In accordance with some embodiments, an electronic device is described.The electronic device comprising a display; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:while the electronic device is operating in a first mode, displaying, onthe display, a first user interface of an application; detecting thatthe electronic device has met criteria for transitioning from the firstmode to a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode: transitioning from the first mode to the second mode;replacing, on the display, the first user interface with a second userinterface including an obscured representation of at least a portion ofthe first user interface of the application; and displaying a timeindicator at a position on the display overlapping at least a portion ofthe obscured representation of the at least a portion of the first userinterface of the application.

In accordance with some embodiments, an electronic device is described.The electronic device comprising a display; means, while the electronicdevice is operating in a first mode, for displaying, on the display, afirst user interface of an application; means for detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode; and means, responsive to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, for: transitioning from the first mode to the second mode;replacing, on the display, the first user interface with a second userinterface including an obscured representation of at least a portion ofthe first user interface of the application; and displaying a timeindicator at a position on the display overlapping at least a portion ofthe obscured representation of the at least a portion of the first userinterface of the application.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing display usage, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods formanaging display usage

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6X illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIG. 7 illustrates a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 8A-8M illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIG. 9 illustrates a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 10A-10I illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIGS. 11A-11B illustrate a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 12A-12I illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIG. 13 illustrates a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 14A-14E illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIG. 15 illustrates a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 16A-16F illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIGS. 17A-17B illustrate a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

FIGS. 18A-18L illustrate exemplary user interfaces with managed displayusage in accordance with embodiments.

FIG. 19 illustrates a flow diagram depicting a method for managingdisplay usage in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing display usage. For example, prolongeddisplay of user interfaces that include non-moving graphical object(e.g., static images) overtime causes screen burn-in or image ghosting.This is particularly true for portable multifunction devices withreduced-size displays, since elements of a displayed user interface areoften displayed repetitively at fixed positions on a display. Techniquesthat thoughtfully manage what is include on a user interface, how it isdisplayed, and when it is displayed minimize screen burn-in and imageghosting. Such techniques can reduce the cognitive burden on a user whoaccesses user interfaces, thereby enhancing productivity. Further, suchtechniques can reduce processor and battery power otherwise wasted onredundant user inputs and excessive display brightness, and improve thewear characteristics of display devices used to display user interfaces.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing displayusage. FIGS. 6A-6X illustrate exemplary devices and techniques formanaging display usage, in accordance with some embodiments. FIG. 7 is aflow diagram illustrating methods of managing display usage, inaccordance with some embodiments. The user interfaces in FIGS. 6A-6X areused to illustrate the processes described below, including theprocesses in FIG. 7. FIGS. 8A-8M illustrate exemplary devices andtechniques for managing display usage, in accordance with someembodiments. FIG. 9 is a flow diagram illustrating methods of managingdisplay usage, in accordance with some embodiments. The user interfacesin FIGS. 8A-8M are used to illustrate the processes described below,including the processes in FIG. 9. FIGS. 10A-10I illustrate exemplarydevices and techniques for managing display usage, in accordance withsome embodiments. FIGS. 11A-11B are a flow diagram illustrating methodsof managing display usage, in accordance with some embodiments. The userinterfaces in FIGS. 10A-10I are used to illustrate the processesdescribed below, including the processes in FIGS. 11A-11B. FIGS. 12A-12Iillustrate exemplary devices and techniques for managing display usage,in accordance with some embodiments. FIG. 13 is a flow diagramillustrating methods of managing display usage, in accordance with someembodiments. The user interfaces in FIGS. 12A-12I are used to illustratethe processes described below, including the processes in FIG. 13. FIGS.14A-14E illustrate exemplary devices and techniques for managing displayusage, in accordance with some embodiments. FIG. 15 is a flow diagramillustrating methods of managing display usage, in accordance with someembodiments. The user interfaces in FIGS. 14A-14E are used to illustratethe processes described below, including the processes in FIG. 15. FIGS.16A-16F illustrate exemplary devices and techniques for managing displayusage, in accordance with some embodiments. FIGS. 17A-17B are a flowdiagram illustrating methods of managing display usage, in accordancewith some embodiments. The user interfaces in FIGS. 16A-16F are used toillustrate the processes described below, including the processes inFIGS. 17A-17B. FIGS. 18A-18L illustrate exemplary devices and techniquesfor managing display usage, in accordance with some embodiments. FIG. 19is a flow diagram illustrating methods of managing display usage, inaccordance with some embodiments. The user interfaces in FIGS. 18A-18Lare used to illustrate the processes described below, including theprocesses in FIG. 19.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,1100, 1300, 1500, 1700, 1900 (FIGS. 7, 9, 11A-11B, 13, 15, 17A-17B, and19). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance. In some examples, anaffordance is displayed as a complication associated with a clock face.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, device 500, ordevice 600.

FIGS. 6A-6X illustrate exemplary techniques for displaying userinterfaces, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 7. In particular, FIGS. 6A-6X illustratetechniques for managing display usage by altering one or more aspects(e.g., visual characteristics) of a displayed user interface upondetermining that the device has met a mode-transition criteria. In someembodiments, the mode-transition criteria are one or more criteria thatare indicative of reduced user activity or reduced user interaction withthe electronic device (e.g., reduced user activity (physical movement)for a predetermined period of time; a lack of user input for apredetermined period of time; detecting a predefined gesture, such as acover gesture over the display, corresponding to a request to transitionmodes). In some embodiments, detecting that the device has met thecriteria includes one or more of: receiving data from one or moresensors (e.g., accelerometer, gyroscope, proximity sensor) correspondingto a user gesture (e.g., wrist-down, wrist-up, palm over display),receiving data from one or more sensors indicating user activity below athreshold activity level, and determining a predetermined period of timehas elapsed without detecting user input at one or more input devices(e.g., touch-screen, rotatable input mechanism, depressible inputmechanism). In some embodiments, a predefined period of time associatedwith a mode-transition criteria differs depending on how display of thepresently displayed user interface was initiated (e.g., a longerpredefined period a of time for a tap input and shorter predefinedperiod a of time for a wrist raise).

Upon determining that a mode-transition criteria has been met, thedevice transitions from a first mode to a second mode (e.g., a low powermode). In some embodiments, while operating in the second mode, device600 conserves energy by operating one or more processors of the deviceat a reduced load, such as by waking (e.g., enabling or turning on) oneor more processors of the device at increased intervals (e.g., a reducerate; less often) compared to operation in the first mode. In someembodiments, a processor includes hardware (e.g., a microprocessor orthe like). In some embodiments, a processor includes one or moresoftware components (e.g., software modules for performing variousfunctions; a module for displaying information from applications on adisplay device; a module for processing sensor data received by thedevice, a module for performing calculations necessary to perform orimplement various features of the device, etc.).

Among the visual characteristics described below that may be alteredupon transitioning device modes is the overall brightness of a displayeduser interface (e.g., average pixel luminance (APL), average lumenoutput, total lumen output, average illuminance, or total illuminance ofthe pixels comprising the user interface on the display; brightnessexpressed in nits, lux, or lumens). To illustrate this, FIGS. 6A-6X (aswell as FIGS. 8A-8M, 10A-10I, 14A-14E, 16A-16F, and 18A-18L) includebrightness scale 630 indicating a brightness level at which eachrespective user interface is displayed by device 600 on display 602. Forexample, as represented by the difference between respective brightnessscales (e.g., position of circular indicator relative to the top(“HIGH”) and bottom (“LOW”) ends of each scale), clock face userinterface 608-1 of FIG. 6A is displayed at a higher brightness level(e.g., greater luminance) than clock face user interface 608-2 of FIG.6B.

Throughout this disclosure, the concept of brightness levels are alsodiscussed with respect to individual graphical elements or groups ofgraphical elements included in various clock face user interfaces (e.g.,affordances, graphical elements included within affordances,complications, clock face elements, backgrounds, indicators, etc.)displayed by device 600 on display 602. Similar to the brightness levelof a clock face user interface, the brightness level of a graphicalelement as displayed within a clock face user interface on display 602may also by varied (e.g., using the techniques described below). Pleasenote, however, that as depicted throughout the figures described below,brightness scale 630 reflects an overall brightness level of arespective clock face user interface (e.g., the entire clock face userinterface being displayed, not the brightness level of individualgraphical elements or groups of graphical elements within the respectiveclock face user interface), unless otherwise noted. Furthermore,brightness scale 630 is not part of any user interface displayed ondevice 600.

In addition to brightness scale 630, the relative displayed brightnessof a clock face user interface and elements constituting the clock faceuser interfaces described below (e.g., graphical objects displayed in oron the user interface, backgrounds, etc.) are also represented by thedepicted shading intensities in each figure (e.g., white or lightergreys indicating more brightly displayed elements; darker greysindicating less brightly displayed elements).

In some embodiments, brightness levels can be adjusted (increased ordecreased) using alpha blending. In some embodiments, decreasing abrightness level includes using alpha blending without altering abacklight of the electronic device to create a simulated or realbacklight level. For instance, the device can alpha blend image datarepresenting a clock face user interface (or a portion of a clock faceuser interface such as an affordance or complication) with anincreasingly opaque black masking layer to increasingly dim the clockface user interface as displayed on the screen (e.g., so that the userinterface fades to black).

In some embodiments, a brightness level of a graphical object in a clockface user interface is changed by altering the shape or composition ofthe graphical object itself. For example, the brightness of a whiteclock hand by may decreased by reducing the thickness of the clock hand(e.g., removing white pixels from the element). In some embodiments, abrightness level of a graphical object is altered (e.g., reduced ordimmed) by replacing solid-colored regions of the object with asimilarly colored outlines of the solid-colored regions. In someembodiments, a brightness level of a graphical object is reduced ordimmed by altering its colors, for example, by replacing lighter colors(e.g., white, light greys, yellows, etc.) with darker colors (black,dark greys, blues, etc.). Any combination of the brightness alteringtechniques described above or similar techniques well-known in the art,may be used for adjusting brightness levels of graphical objects andclock face user interfaces in accordance with the embodiments describedbelow.

Turning now to FIG. 6A, device 600 includes display 602, rotatable anddepressible input mechanism 604 (e.g., rotatable and depressible inrelation to a housing or frame of the device), and button 606. In theembodiments described below, device 600 is a wearable device, such as asmartwatch. In some embodiments, device 600 is a smart phone, a tablet,or other computing system including a display device (e.g., displayscreen, projection device, and the like). In some embodiments, device600 includes one or more features of devices 100, 300, or 500.

At FIG. 6A, while operating in a standard display mode, device 600displays clock face user interface 608-1 (e.g., a higher powerconsumption user interface) on display 602 at a standard display modebrightness level. In some embodiments, while device 600 continues tooperate in the standard display mode, the standard display modebrightness level is reduced in response to detecting reduced ambientlight levels at one or more sensor of device 600 (e.g., lower ambientlight levels result in lower display brightness levels as describedbelow in more detail with respect to FIGS. 10D-10E).

As illustrated in FIG. 6A, clock face user interface 608-1 includesanalog indication of time 610 (e.g., a representation of analog clockhands displaying current hour, minute, and second values relative totime scale 612), and multiple affordances (e.g., clock facecomplications). In some embodiments, each affordance is associated withan application on device 600 (e.g., the affordance launches anassociated application upon selection; the affordance displaysinformation from the associated application).

Date affordance 614 indicates a current date and a description of anupcoming calendar event (e.g., “8:00 AM YOGA GYM”). World clockaffordance 616 indicates a geographic location (e.g., “MAD” for Madrid,Spain), a time associated with the geographic location (e.g., an analogclock dial with hour and minute hands), and an indication of day, night,sunset, or sunrise (e.g., indicating that it is day-time in Madrid basedon the light-colored shade of the background (e.g., darker shadesindicated later in the day)). In some embodiments, world clockaffordance 616 includes an offset to a local time. In some embodiments,the position of the location indicator moves to avoid overlapping orinterfering with the clock hands as they progress around the world clockdial.

Compass affordance 618 includes graphical (e.g., a compass needlegraphic), textual (e.g., “NW”), and numerical (“330” degrees) indicatorsof a cardinal or intercardinal direction which update as the orientationof device 600 (or the orientation a second device coupled to device 600)changes.

Timer affordance 620 includes a numerical indicator (e.g., “14:59”) andradial markings, each indicating a remaining time associated with atimer application. The radial markings are sequentially altered (e.g.,visually de-emphasized in size and/or color) such that the ratio ofaltered to unaltered radial markings is proportional to the timeremaining on a decrementing counter associated with the timerapplication.

Heart rate affordance 622, moon affordance 624, stopwatch affordance626, and workout affordance 628 are displayed at the corners of clockface user interface 608-1. As depicted in FIG. 6A, stopwatch affordance626 includes a numeric indicator of an elapsed time (e.g., incrementingseconds, minutes, and milliseconds) associated with a stopwatchapplication on device 600.

FIG. 6B illustrates device 600 after determining that a mode changecriteria has been met and, in response, transitioning out of thestandard display mode (e.g., device 600 is in a transitional mode orstate). In some embodiments, device 600 determined that the mode changecriteria were met after not detecting user inputs for a predeterminedtime (e.g., 60 seconds).

At FIG. 6B, while in a mode transitional state, device 600 displaysclock face user interface 608-2 on display 602 (e.g., device 600displays a transitional interface). Clock face user interface 608-2 is aframe of an animation (e.g., a sequence of frames or images)illustrating clock face user interface 608-1 (e.g., a higher powerconsumption user interface) visually morphing into a corresponding lowerpower consumption user interface (e.g., clock face user interface 608-3as depicted in FIG. 6C). In some embodiments, device 600 displays aplurality of animation frames (e.g., transitional interfaces) whileoperating in a transitional state between device modes (e.g., a standardpower display mode and a low power display mode).

As depicted in FIG. 6B, and as discussed above, device 600 displaysclock face user interface 608-2 on display 602 at a lower brightnesslevel than clock face user interface 608-1 (e.g., the overall brightnesslevel or the average of the brightness values of pixels constitutingclock face user interface 608-2 on display 602 is less than thebrightness level of clock face user interface 608-1 on display 602 asdepicted in FIG. 6A). Clock face user interface 608-2 includes severalmodifications relative to clock face user interface 608-1 (e.g., changesto brightness and positioning of individual elements (e.g.,affordances), removal of content, etc.). However, since clock face userinterface 608-2 represents an intermediate visual state, thesedifferences will be discussed in more detail below in reference to FIG.6C.

FIG. 6C illustrates device 600 in low power display mode (e.g., afterthe transition from standard display mode to low power display mode hasconcluded). At FIG. 6C, while operating in low power display mode,device 600 displays clock face user interface 608-3 (e.g., lower powerconsumption user interface) on display 602. Clock face user interface608-3 is displayed at a lower brightness level than clock face userinterface 608-1 (and clock face user interface 608-2). In someembodiments, clock face user interface 608-3 is displayed at a fixedpercentage of the brightness level at which device 600 displays clockface user interface 608-1. In some embodiments, clock face userinterface 608-3 is displayed at a brightness level based at least inpart on an ambient light level detected by one or more sensor of device600 (e.g., higher ambient light levels result in higher brightnesslevels while in low power display mode).

Clock face user interface 608-3 includes less content than clock faceuser interface 608-1. As depicted in FIG. 6C, analog indication of time610 does not include a seconds hand, date affordance 614 does notinclude a description of an upcoming calendar event (e.g., “8:00 AM YOGAGYM”), time scale 612 includes fewer tick marks, compass affordance 618does not include a textual (e.g., “NW”) or a numerical (“330” degrees)indicators of direction, and timer affordance 620 does not includesseconds data. Additionally, clock face user interface 608-3 does notinclude an affordance corresponding to heart rate affordance 622 (e.g.,heart rate affordance 622 was removed in response to device 600transitioning from standard display mode to low power display mode).

In addition to including less or reduced content, corresponding elementsin clock face user interface 608-3 are displayed by device 600differently than they were previously displayed in clock face userinterface 608-1. In FIG. 6C, the hour and minute hands of analogindication of time 610 are displayed in two colors rather than one(e.g., each hand includes an inner lighter colored region outlined by adarker colored region). Additionally, as depicted in FIG. 6C, the pointof rotation of analog indication of time 610 (e.g., the stationaryelement about which the clock hands rotate) is displayed at lowerbrightness level (e.g., a darker color) relative to the clock hands(e.g., compared to the depiction of the hands and point of rotation ofthe analog indication of time 610 in clock face user interface 608-1 ofFIG. 6A).

Device 600 displays each affordance in clock face user interface 608-3at reduced brightness levels (e.g., low power display mode brightnesslevels) compared to their respectively displayed brightness levels inFIG. 6A (e.g., standard display mode brightness levels). As depicted inFIG. 6C, date affordance 614, world clock affordance 616, compassaffordance 618, timer affordance 620, moon affordance 624, stopwatchaffordance 626, and workout affordance 628 are displayed by device 600on display 602 at dimmer (lower) brightness levels (e.g., as indicatedby darker coloring of each affordance in FIG. 6C compared to FIG. 6A).

As depicted in FIG. 6C, the change in brightness levels betweencorresponding elements (e.g., affordances) in clock face user interfaces608-1 and 608-3 is not uniform (e.g., some elements are dimmed more thanothers). Compared to their respective depictions in clock face userinterface 608-1 in FIG. 6A, as depicted in clock face user interface608-3 in FIG. 6C, world clock affordance 616 has dimmed more than dateaffordance 614, compass affordance 618, and timer affordance 620.Similarly, analog indication of time 610 has dimmed less than all otheraffordances depicted in clock face user interface 608-3 (e.g., analogindication time 610 still includes brightly displayed portions whereasthe affordances do not). Likewise, the point of rotation of analogindication of time 610 (e.g., the stationary element about which theclock hands rotate) has dimmed more than the clock hands.

As depicted in FIG. 6C, device 600 displays each affordance in clockface user interface 608-3 at a reduced size compared to their respectivesize in clock face user interface 608-1 (e.g., corresponding outlinesrepresent the size of affordances in clock face user interface 608-1while device is in standard display mode). As depicted in FIG. 6C (e.g.,while the device is in low power display mode), date affordance 614,world clock affordance 616, compass affordance 618, timer affordance620, moon affordance 624, and stopwatch affordance 626 have shrunk inplace relative to their depiction in FIG. 6A (e.g., the center of eachaffordance remains in the same position relative to the edges of display602 in both FIG. 6A and FIG. 6C). In some embodiments, one or moreaffordances may instead shrink towards a common central point (e.g.,translate towards the center of display 602 or towards the point ofrotation of analog indication of time 610 (e.g., as describe withrespect to FIG. 8M below).

At FIG. 6C, while operating in low power display mode, device 600detects user input 632-1 (e.g., an upward swipe on display 602). Upondetecting user input 632-1, device 600 maintains display of clock faceuser interface 608-3 (e.g., device 600 does not respond to the swipeinput while operating in low power display mode). In some embodiments,rather than ignoring user input 632-1 while operating in the low powerdisplay mode, device 600 responds by displaying a watch user interfaceincluding a settings menu for changing various device settings (e.g., asdescribed with respect to FIGS. 6J-6K below).

FIGS. 6D-6H illustrate device 600 transitioning from low power displaymode back to standard display mode. While the description of FIGS. 6D-6Hbelow discusses device 600 transitioning in response to detectingrotational input, FIG. 6D also illustrates device 600 detecting severalother user inputs (e.g., tap gestures 632-3, 632-4, and 632-5), eachwhich can independently cause device 600 to initiate a transition fromlow power display mode to the standard display mode. In someembodiments, upon detecting a tap gestures 632-3 or 632-5 while in lowpower display mode, device 600 transitions to standard display mode andlaunches the corresponding application (e.g., workout and calendarapplications, respectively).

At FIG. 6D, while operating in low power display mode, device 600detects user input 632-2 (e.g., rotation of rotatable and depressibleinput mechanism 604). In response to detecting user input 632-2, device600 initiates a transition back to standard display mode, displayingclock face user interface 608-5 as depicted in FIG. 6E (e.g., device 600displays a transitional interface similar to clock face user interface608-2 while in a mode transitional state). Clock face user interface608-5 is a frame of an animation (e.g., a sequence of frames or images)illustrating clock face user interface 608-4 (e.g., a lower powerconsumption interface) visually morphing into a corresponding higherpower consumption user interface (e.g., clock face user interface 608-8as depicted in FIG. 6H).

At FIG. 6E, while device 600 displays clock face user interface 608-5 atthe same brightness level as clock face user interface 608-4 in FIG. 6D(e.g., device 600 maintains the low power display mode brightness levelwhile in a mode transitional state). As depicted in FIG. 6E, dateaffordance 614, world clock affordance 616, compass affordance 618,timer affordance 620, moon affordance 624, and stopwatch affordance 626have enlarged relative to their previously displayed size in clock faceuser interface 608-4 (e.g., clock face user interface 608-5 includesaffordances displayed larger than their respective sizes in clock faceuser interface 608-4).

At FIG. 6E, device 600 detects user input 632-6 (e.g., device 600continues to detect rotation of rotatable and depressible inputmechanism 604). In response to detecting user input 632-6, device 600displays clock face user interface 608-6 as depicted in FIG. 6F (e.g., alower power consumption user interface similar to clock face userinterface 608-1). In contrast to clock face user interface 608-1 asdepicted in FIG. 6A, device 600 displays user interface 608-6 at thesame brightness level as clock face user interface 608-5 in FIG. 6E(e.g., device 600 maintains the low power display mode brightness levelwhile in a mode transitional state).

The sequence of FIGS. 6F, 6G, and 6H illustrate device 600 graduallybrightening the displayed clock face user interface in response todevice detecting additional rotational inputs at rotatable anddepressible input mechanism 604 (e.g., 632-7, 632-8, and 632-9). At FIG.6H, device 600, while in standard display mode, displays clock face userinterface 608-8 (e.g., device 600 has completely transitioned back tooperating in the standard display mode). Clock face user interface 608-8includes substantially the same content as clock face user interfaces608-1 and 608-7, however, analog indication of time 610, timeraffordance 620, and stopwatch affordance 626 have been updated toreflect that time has elapsed since device 600 displayed clock face userinterface 608-1.

In some embodiments, the transition from low power display mode tostandard display mode described above with respect to FIGS. 6D-6H isinitiated in response to receiving user input 632-3, user input 632-4,or user input 632-5 (e.g., taps gestures at various locations on clockface user interface 608-4 as depicted in FIG. 6D). In some embodiments,in response to detecting a tap gesture input (e.g., 632-3, 632-4, 632-5)while operating in low power display mode, device 600 displays anemphasis animation prior to displaying clock face user interface 608-5.In some embodiments, the emphasis animation includes further dimming andshrinking of elements of the clock face user interface prior toincreasing their respective size, brightness, and content (e.g., asdescribed below with respect to FIGS. 8D-8F).

At FIG. 6H, device 600 detects user input 632-9 (e.g., a tap inputgesture) at a location corresponding to workout affordance 628. Inresponse to detecting user input 632-9, device 600 displays workoutapplication user interface 608-9 as depicted in FIG. 6I (e.g., while instandard display mode, in response to detecting a tap gesture at alocation corresponding to an affordance associated with an application,device 600 launches the respective application).

At FIG. 6I, device 600 detects user input 632-10 (e.g., a depression ofrotatable and depressible input mechanism 604). In response to detectinguser input 632-10, device 600 displays clock face user interface 608-10as depicted in FIG. 6J. As depicted in FIG. 6J, analog indication oftime 610, timer affordance 620, and stopwatch affordance 626 haveupdated to reflect that additional time has elapsed since device 600displayed clock face user interface 608-8 as depicted in FIG. 6H.

At FIG. 6J, while operating in standard display mode, device 600 detectsuser input 632-11 (e.g., an upward swipe gesture on display 602). Inresponse to detecting input 632-11, device 600 displays user interface608-11 as depicted in FIG. 6K. Watch user interface 608-11 includes amenu for altering (e.g., toggling; enabling and disabling) variousdevice settings. User interface 608-11 includes theatre mode affordance634 for enabling a theater mode setting (e.g., a device setting thatprevents display 602 from turning on in response to detected movement,so that display 602 remains off in movie theaters, concerts, publicevents, or in other scenarios where the user of device 600 desires toavoid incidental activation the display 602).

At FIG. 6K, device detects user input 632-13 at theater mode affordance634. In response to detecting user input 632-13, device 600 enablestheater mode. As illustrated in FIG. 8L, while in theater mode, device600 turns display 602 off rather than displaying a corresponding lowerpower consumption user interface, when for example, device 600 fails todetect user input for a predetermined period of time (e.g.,mode-transition criteria as describe above).

FIG. 6M illustrates device 600 while attached to charger 636. Whileattached to charger 636 as depicted in FIG. 8M, device 600 turns display602 off rather than displaying a corresponding lower power consumptionuser interface, when for example, device 600 fails to detect user inputfor a predetermined period of time (e.g., mode-transition criteria asdescribed above).

FIG. 6N illustrates device 600 displaying watch user interface 608-12,which is a settings interface. Watch user interface 608-12 includes lowpower mode affordance 638 for disabling low power mode and privacyaffordance 640 for disabling the removal of sensitive content whendevice 600 operates in low power mode. When low power mode is disabled,rather than transition from a standard display mode to low-power displaymode as described with respect to FIGS. 6A-6D, device turns off display602. When removal of sensitive content is disabled, device 600 refrainsfrom removing content deemed sensitive (e.g., upcoming calendar event(e.g., “8:00 AM YOGA GYM”) of date affordance 614 in FIG. 6A is includedin FIGS. 6B-6C) upon transitioning from standard display mode tolow-power display mode.

FIGS. 6O-6X, depicts device 600 displaying various clock face userinterfaces in standard display mode and low power display mode toillustrate the changes that occur when device 600 transitions betweenmodes.

At FIG. 6O, while operating in standard display mode, device 600displays clock face user interface 608-13 (e.g., a higher powerconsumption user interface). Clock face user interface 608-13 includesdigital indication of time 642 (e.g., a digital clock indicating hourand minute values), date indicator 644, calendar affordance 646, timeraffordance 620, workout affordance 628, compass affordance 618, andworld clock affordance 616.

At FIG. 6P, while operating in low power display mode (e.g., afterdevice 600 determines that one or more mode-transition criteria has beenmet), device 600 displays clock face user interface 608-14 (e.g., a lowpower consumption user interface corresponding to clock face userinterface 608-13 as depicted in FIG. 6O). As depicted in FIG. 6P, device600 displays clock face user interface 608-14 on display 602 at a lowerbrightness compared to clock face user interface 608-13. Additionally,as depicted in FIG. 6P, digital indication of time 642, date indicator644, calendar affordance 646, workout affordance 628, compass affordance618, and world clock affordance 616 have dimmed, shifted, and/or shrunkrelative to their depiction in FIG. 6O. Additionally, as depicted inFIG. 6P, the colon (e.g., “:”) of digital indication of time 642 isdisplayed at lower brightness level (e.g., a darker color) relative tohour and minute numerals (e.g., compared to the depiction of the digitalindication of time 642 in watch user interface 608-13 of FIG. 6O).

At FIG. 6Q, while operating in a standard display mode, device 600displays clock face user interface 608-15 on display 602. Clock faceuser interface 608-15 includes digital indication of time 642 andanimated object 648. Animated object 642, as depicted in FIG. 6Q, is afirst frame (e.g., image) of animated sequence of frames (e.g., images)displayed by device 600 depicting animated object 648 moving (e.g.,blooming; increasing in size).

At FIG. 6R, while operating in low power display mode (e.g., afterdevice 600 determines that one or more mode-transition criteria has beenmet), device 600 displays clock face user interface 608-16 (e.g., a lowpower consumption user interface corresponding to clock face userinterface 608-15 as depicted in FIG. 6R). As depicted in FIG. 6R, device600 displays clock face user interface 608-16 on display 602 at a lowerbrightness compared to clock face user interface 608-15. Additionally,as depicted in FIG. 6R, digital indication of time 642 and dateindicator 644 have dimmed, shifted, and shrunk relative to theirdepiction in clock face user interface 608-15 in FIG. 6Q. In someembodiments, animated object 648 as depicted in user interface 608-15 isa second frame (e.g., different from the first frame) selected from thesame animated sequence of images displayed by device 600 while device600 is in standard display mode.

At FIG. 6S, while operating in a standard display mode, device 600displays clock face user interface 608-17 on display 602. Clock faceuser interface 608-17 includes analog indication of time 610 displayedover a background including first color gradient 650 extending clockwisefrom the hour to the minute hand (e.g., transitioning from dark tolighter blues), second color gradient 652 extending clockwise from theminute hand to the second hand (e.g., transitioning from dark to lighterreds), and third color gradient 654 extending clockwise from the secondhand to the hour hand (e.g., transitioning from dark to lighter greens).In some embodiments, the colors included within first color gradientportion 650 are based upon a color of a watchband of device 600.

At FIG. 6T, while operating in a low power display mode (e.g., afterdevice 600 determines that one or more mode-transition criteria has beenmet), device 600 displays clock face user interface 608-18 on display602. As depicted in FIG. 6T, device 600 displays clock face userinterface 608-18 on display 602 at a lower brightness compared to clockface user interface 608-17. In FIG. 6T, relative to clock face userinterface 608-17, the second hand of analog indication of time 610 hasbeen removed, second color gradient 652 and third color gradient 654have been replaced by greyscale gradient 656, extending clockwise fromthe minute hand to the hour hand, the grey scale gradient starting inblack at the minute hand and gradually transiting to lighter shades ofgrey in the clockwise direction. Additionally, as depicted in FIG. 6T,the point of rotation of analog indication of time 610 (e.g., thestationary element about which the clock hands rotate) is displayed atlower brightness level (e.g., a darker color) relative to the clockhands (e.g., compared to the depiction of the hands and point ofrotation of the analog indication of time 610 in clock face userinterface 608-17 of FIG. 6S). Further, as depicted in FIG. 6T, analogindication of time 610 is has been modified (e.g., similar to FIG. 6B asdescribed above, the hands consist of two shades rather than one).

At FIG. 6U, while operating in standard display mode, device 600displays clock face user interface 608-19 (e.g., a higher powerconsumption user interface). Clock face user interface 608-19 includesanalog indication of time 610 and background object 658 (e.g., a solidor single-colored object, color indicated by hatching).

At FIG. 6V, while operating in low power display mode (e.g., afterdevice 600 determines that one or more mode-transition criteria has beenmet), device 600 displays clock face user interface 608-20 (e.g., alower power consumption user interface corresponding to clock face userinterface 608-19 as depicted in FIG. 6U). As depicted in FIG. 6V, device600 displays clock face user interface 608-20 on display 602 at a lowerbrightness compared to clock face user interface 608-19, backgroundobject 658 has been replaced with outline object 659 (e.g., outline ofbackground object 658). Additionally, as depicted in FIG. 6V, the pointof rotation of analog indication of time 610 (e.g., the stationaryelement about which the clock hands rotate) is displayed at lowerbrightness level (e.g., a darker color) relative to the clock hands(e.g., compared to the depiction of the hands and point of rotation ofthe analog indication of time 610 in clock face user interface 608-19 ofFIG. 6U). Further, as depicted in FIG. 6V, analog indication of time 610is has been modified (e.g., similar to FIG. 6B as described above, thehands consist of two shades rather than one).

At FIG. 6W, while operating in standard display mode, device 600displays clock face user interface 608-21 (e.g., a higher powerconsumption user interface). Clock face user interface 608-21 includesanalog dial 660, representing a twenty-four hour time period, and insettime indication 662. In FIG. 6W, analog dial 660 includes a circulardial with hour markers evenly spaced angularly around the perimeter ofthe circle, representing 24 hours. As depicted in FIG. 6W, thebackground of analog dial 660 includes an angular gradient that has agradual transition from a first color to a second color. In FIG. 6W,inset time indication 662 includes a digital clock indicating a currenttime (8:00 pm). At 8:00 pm, inset time indication 1604 is displayed at afirst position on clock face user interface 608-21 inside analog dial660. As time progresses, inset time indication 1604 moves along acircular path within analog dial 1602.

Clock face user interface 608-21 includes a representation 664indicating a position of the Sun (e.g., relative to a location on Earth(e.g., corresponding to the current location of device 600)) at thedisplayed time. The position of representation 664 with respect toanalog dial 660 indicates the same time indicated by inset timeindication 1604 (e.g., the current time). As time progresses,representation 664 moves around a circular path 666 that has a commonorigin with the circular path around which inset time indication 662moves. As illustrated in FIG. 6W, inset time indication 662 andrepresentation 664 are separated by 180 degrees around the common originof their paths. Additionally, clock face user interface 608-21 alsoincludes ultraviolet index affordance 668, temperature affordance 670,air quality index affordance 672, and weather conditions affordance 674positioned near the corners of display 602.

At FIG. 6X, while operating in low power display mode (e.g., afterdevice 600 determines that one or more mode-transition criteria has beenmet), device 600 displays clock face user interface 608-22 (e.g., alower power consumption user interface corresponding to clock face userinterface 608-21 as depicted in FIG. 6W). As depicted in FIG. 6X, device600 displays clock face user interface 608-22 on display 602 at a lowerbrightness compared to clock face user interface 608-21. As depicted inFIG. 6X, the angular gradient of the background of analog dial 660 hasdarkened (e.g., dimmed) more than the hour markers and the affordancespositioned at the corners of clock face user interface 608-22 (e.g.,relative to their respective appearance FIG. 6W). Additionally, haloobject 676 is displayed around representation 664 (e.g., to increasecontrast between the representation of the sun and the darkenedgradient). In some embodiments, representation 664 is displayed at thesame brightness while device is operating in standard display mode andlow power display mode.

FIG. 7 is a flow diagram illustrating a method for managing displayusage using an electronic device in accordance with some embodiments.Method 700 is performed at a device (e.g., 100, 300, 500, 600) with adisplay. Some operations in method 700 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 700 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

In general, different brightness levels can be achieved using varioustechniques, which can be employed separately or concurrently. In someembodiments, the brightness level of a graphical element is changed bychanging (e.g., brightening, dimming) the brightness of some (or all)pixels of the graphical element. In some embodiments, the brightnesslevel of the graphical element is changed by modifying the graphicalelement so that fewer (or more) pixels are lit up, such as by thinning(or thickening) lines of the graphical element, and removing (or adding)a background of the graphical element, reducing (or enlarging) a size ofthe graphical element.

While the electronic device (e.g., 600) is in a first mode (e.g., ahigher power consumption mode), the electronic device (e.g., 600)displays (702) on the display, a first user interface (e.g., a clockface of a smart watch; 608-1) including a first time indicator (704) anda first graphical object (706). The first time indicator (704) (e.g.,hands of 610 at FIG. 6A) (e.g., an analog clock hand (hour, minute,second hand); a digital clock numeral (hour, minute, second numerals))is displayed at a first brightness level (e.g., average pixel luminance(APL), average lumen output, total lumen output, average illuminance, ortotal illuminance of the indicator on the display; brightness expressedin nits, lux, or lumens). The first graphical object (706) (e.g., centerof 610 at FIG. 6A; 614, 616, 618, 620 at FIG. 6A) (e.g., an affordance;an affordance representing a first application; an interactive graphicalobject; an affordance displayed as a complication associated with aclock face; a non-updating graphical element (rotation point of a clockhand; colon separating digital clock numerals)) is displayed at a secondbrightness level (e.g., a brightness level that is the same as the firstbrightness level; a brightness level that is different than the firstbrightness level).

The electronic device, (e.g., 600) detects (708) that the electronicdevice has met criteria for transitioning from the first mode to asecond mode (e.g., one or more criteria that are indicative of reduceduser activity or reduced user interaction with the electronic device(e.g., determining reduced user activity (physical movement) for apredetermined period of time, determining a lack of user input for apredetermined period of time, detecting a predefined gesture). In someembodiments, detecting that the electronic device has met the criteriaincludes one or more of: receiving data from one or more sensors (e.g.,accelerometer, gyroscope, proximity sensor) corresponding to a usergesture (e.g., wrist-down, wrist-up, palm over display), receiving datafrom one or more sensors indicating user activity below a thresholdactivity level, determining a predetermined period of time has elapsewithout device receiving user input at one or more input devices (e.g.,touch-screen, rotatable input mechanism, depressible input mechanism).

In response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, the electronicdevice (e.g., 600) transitions (710) the electronic device from thefirst mode (e.g., a higher power consumption mode) to the second mode(e.g., a lower power consumption mode). The first mode and the secondmode are different modes in which the electronic device can operate. Insome embodiments, the overall brightness of the display in the firstmode is more than the overall brightness of the display in the secondmode when displaying a corresponding user interface. In someembodiments, a rate of display refresh is higher in the first mode ascompared to the second mode. In some embodiments, one or more processorof the electronic device are awake for a higher percentage of time whenthe device is in the first mode as compared to when the device is in thesecond mode. In some embodiments, the one or more processors of theelectronic device wake up more frequently over a duration of time whenthe device is in the first mode as compared to when the device is in thesecond mode. In some embodiments, more portions of the one or moreprocessors of the electronic device are running when the device is inthe first mode as compared to when the device is in the second mode. Insome embodiments, the electronic device employs processor powermanagement techniques (e.g., slowing down or turning off a core clock,slowing down or turning off a bus clock, reducing the main CPU voltage(VCC) in the second mode that are not employed in the first mode.

While the electronic device (e.g., 600) is in the second mode, theelectronic device (e.g., 600) displays (712) on the display (e.g., 602),a second user interface (e.g., 608-3) including: a second time indicator(714) and a second graphical object (716).

The second time indicator (714) indicates the current time (hands of 610at FIG. 6C) (e.g., an analog clock hand (hour, minute, second hand); adigital clock numeral (hour, minute, second numerals)). The second timeindicator is displayed at a third brightness level that is lower thanthe first brightness level, at which the first time indicator waspreviously displayed, by a first amount.

The second graphical object (716) corresponds to the first graphicalobject (e.g., center of 610 at FIG. 6C; 614, 616, 618, 620 at FIG. 6C)(e.g., a non-interactive version of the first graphical object; avisually distinct graphical object representing to the same applicationas the first graphical object; a graphical object including a subset ofthe data included in the first graphical object (only mm remainingrather than mm:ss remaining)). The second graphical object is displayedat a fourth brightness level that is lower than the second brightnesslevel, at which the first graphical object was previously displayed, bya second amount that is different from the first amount of difference inbrightness between the first brightness level and the second brightnesslevel.

Displaying the time indicator at a reduced brightness reduces powerusage and improves the battery life of the device. Displaying thegraphical object at a reduced brightness reduces power usage andimproves the battery life of the device. Reducing the brightness of theindicator and the graphical object by different amounts enables thedevice to conserve more power by significantly reducing the brightnessof the less relevant visual element (e.g., the graphical object) whilestill displaying the other visual element (e.g., the time indicator) ata brightness that leaves the element more perceptible.

In some embodiments, a first display brightness of the display (e.g.,602 at FIG. 6A) while displaying the first user interface (e.g., a clockface of a smart watch; 608-1) while the electronic device is in thefirst mode (e.g., a higher power consumption mode) is more than a seconddisplay brightness of the display (e.g., 602 at FIG. 6C) whiledisplaying the second user interface while the electronic device is inthe second mode (e.g., a lower power consumption mode). Thus, theoverall brightness of the display is reduced when displaying the seconduser interface while the electronic device is in the second mode ascompared to displaying the first user interface while the electronicdevice is in the first mode. Reducing the overall brightness of thedisplay reduces power usage and improves the battery life of the device,while still enabling the user to access the device.

In some embodiments, the second display brightness (e.g., 602 at FIG.6C) is selected based on the first display brightness (e.g., 602 at FIG.6A). In some embodiments, the electronic device selects the seconddisplay brightness by reducing the first display brightness by apredetermined amount or percentage. Selecting the second displaybrightness based on the first display brightness allows foraccommodating user preferences and visual requirements while reducingpower usage and improving the battery life of the device.

In some embodiments, the second display brightness (e.g., 602 at FIG.6C) is selected based on at least an environmental brightness level(e.g., ambient light level). In some embodiments, when the electronicdevice detects a first level of ambient light (e.g., a high level), theelectronic device selects the second display brightness to be brighterthan when the electronic device detects a second level of ambient light(e.g., a low level) that is less bright than the first level of ambientlight. As a result, the electronic device adapts the second brightnesslevel to the ambient light. In some embodiments, the amount of dimmingincreases as the environmental brightness increases and the amount ofdimming decreases as the environmental brightness decreases (e.g., basedon a magnitude of change in the environmental brightness level). In someembodiments, the amount of dimming decreases as the environmentalbrightness increases and the amount of dimming increases as theenvironmental brightness decreases (e.g., based on a magnitude of changein the environmental brightness level). In some embodiments, selectingthe second display brightness based on the environmental brightnesslevel includes performing one or more of the methods described withrespect to method 1100 and FIGS. 11A-11B. Selecting the second displaybrightness based on an environmental brightness level enables the deviceto reduce the display brightness while still leaving the contents of thedisplay visible to the user. Reducing the display brightness reducespower usage and improves the battery life of the device.

In some embodiments, the first graphical object is a stationarygraphical element (e.g., center of 610 at FIG. 6A; colon separatingnumerals of 642 at FIG. 6O) and the first time indicator is a movinggraphical object (e.g., a non-stationary graphical object; hands of 610at FIG. 6A; numerals of 642 at FIG. 6O). The first amount of differencein brightness is less than the second amount of difference inbrightness. In some embodiments, graphical elements that are stationaryon the display over a period of time are dimmed more than graphicalelements that are not stationary on the display over the same period oftime. In some embodiments, the electronic device dims watch hands thatindicate time (and are not stationary) less than icons for activatingapplications (that are stationary). Dimming stationary graphicalelements more than non-stationary graphical elements allows the deviceto mitigate the negative effects of displaying the same content at thesame location on the display, such as display burn-in, while at the sametime reducing the display brightness. Reducing the display brightnessreduces power usage and improves the battery life of the device.

In some embodiments, the first graphical object is a complication (e.g.,614, 616, 618, and 620 at FIG. 6A) (e.g., a watch face complication; anelement of the watch face that is not associated with providing anindication of time) and the first amount of difference in brightness isless than the second amount of difference in brightness (e.g.,difference between 610 and 616 in FIGS. 6A and 6C).

A complication refers to any clock face feature other than those used toindicate the hours, minutes, or seconds of a current time associatedwith the device. In some embodiments, complications provide dataobtained from an application. In some embodiments, a complicationincludes an affordance that when selected launches a correspondingapplication. In some embodiments, a complication is displayed at afixed, predefined location on the display while the device is in aparticular power consumption mode. In some embodiments, in response todetecting a sequence of one or more inputs, the device may change oredit an aspect of a complication. For example, this could be used tochange application data displayed by an application complication. Insome embodiments, the complication may indicate a first set ofinformation obtained by an application (e.g., application data. Forexample, if the application is a weather application, a set ofinformation could be a forecasted weather condition, a currenttemperature, etc.), and upon editing, the complication could be updatedto indicate a second set of information from the same application (e.g.,if the application is a weather application, the display could be editedfrom showing a current temperature to showing current precipitation). Insome embodiments, in response to detecting a sequence of one or moreinputs, the device may change or edit a complication to indicate a setof information from a different application (e.g., if the application isa weather application, the display could be edited from showing weatherto showing data from a calendar application).

In some embodiments, a first dimming ratio between first brightnesslevel and the third brightness level is different from a second dimmingratio between the second brightness level and the fourth brightnesslevel (e.g., difference between 610 and 616 in FIGS. 6A and 6C). In someembodiments, the first dimming ratio of third brightness level to firstbrightness level is a first value (e.g., 1:2 (½; 50%); 1:3; 1:4) and thesecond dimming ratio of fourth brightness level to second brightnesslevel to is a second value (e.g., 1:4 (¼; 25%); 1:5; 1:6)) that isdifferent from the first value.

In some embodiments, the first user interface (e.g., a clock face of asmart watch; 608-1) displayed while the electronic device is in thefirst mode includes a third graphical object (e.g., 616 at FIG. 6A)displayed at a fifth brightness level that is higher than the firstbrightness level. The second user interface (e.g., 608-3) displayedwhile the electronic device is in the second mode includes a fourthgraphical object displayed at a sixth brightness level, the fourthgraphical object corresponding to the third graphical object (616 atFIG. 6C) (e.g., a non-interactive version of the third graphical object;a visually distinct graphical object representing to the sameapplication as the third graphical object; a graphical object includinga subset of the data included in the third graphical object (only mmremaining rather than mm:ss remaining)). In some embodiments, adifference in brightness between the first brightness level (e.g., usedto display the first graphical object) and the fourth brightness level(e.g., used to display the second graphical object) is less than adifference in brightness between the fifth brightness level (e.g., usedto display the third graphical object) and the sixth brightness level(e.g., used to display the fourth graphical object). In someembodiments, the third graphical object is significantly brighter thanthe first graphical object and, as a result, the third graphical objectis dimmed more than the first graphical object when transitioning todisplaying the second user interface in the second mode. Dimmingbrighter graphical elements more less bright graphical elements allowsthe device reduce the brightness of elements that more significantlyaffect battery consumption and to mitigate the negative effects ofdisplaying content at the same location on the display, such as displayburn-in, while at the same time reducing the display brightness.Reducing the display brightness reduces power usage and improves thebattery life of the device.

In some embodiments, while displaying the first user interface (e.g.,608-1, 1008-4) while the electronic device is in the first mode, theelectronic device (e.g., 600) detects (e.g., using one or more lightsensors) a change (e.g., reduction) in environmental brightness level(e.g., change in ambient light, without detecting that the electronicdevice has met criteria for transitioning from the first mode to thesecond mode). In some embodiments, while displaying the first userinterface (e.g., 608-1, 1008-4) while the electronic device is in thefirst mode, in response to detecting the change (e.g., reduction) inenvironmental brightness level (e.g., ambient light) (e.g., withoutdetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode), changing (e.g.,reducing) the brightness at which the first user interface is displayedon the display without transitioning the electronic device to the secondmode (e.g., 1008-4, 1008-5). In some embodiments, the electronic devicedetermines that the amount of ambient light has been reduced and makes acorresponding change in the brightness at which the first user interfaceis displayed. In some embodiments, changing (e.g., reducing) thebrightness at which the first user interface is displayed does notchange the displayed content the first user interface other thanbrightness (e.g., does not change a size of visual elements, does notchange the information displayed). In some embodiments, the amount ofdimming increases as the environmental brightness increases and theamount of dimming decreases as the environmental brightness decreases(e.g., based on a magnitude of change in the environmental brightnesslevel). In some embodiments, the amount of dimming decreases as theenvironmental brightness increases and the amount of dimming increasesas the environmental brightness decreases (e.g., based on a magnitude ofchange in the environmental brightness level). Changing the brightnessof the display based on environmental brightness allows the contents ofthe display to be more easily visible in bright ambient lightenvironments, thereby providing the user with improved visual feedback,while reducing battery usage in reduced ambient light environments.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device). Reducing the displaybrightness reduces power usage and improves the battery life of thedevice.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes removing (e.g., ceasing todisplay) at least some content (e.g., 622) from the display. In someembodiments, one or more visual elements that were displayed in thefirst mode cease to be displayed as a result of transitioning to thesecond mode. Removing content from the displays enables the device toconserve battery power by avoiding energizing the pixels that thecontent previously used (e.g., turning off the pixels). Avoidingenergizing pixels of the display reduces the display brightness.Reducing the display brightness reduces power usage and improves thebattery life of the device.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes removing (e.g., ceasing todisplay) one or more complications (e.g., 622) from the display. In someembodiments, one or more complications that were displayed in the firstmode cease to be displayed as a result of transitioning to the secondmode.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes removing (e.g., ceasing todisplay) a first set of content of one or more complications from thedisplay (e.g., event description of 614, directional data of 618, andseconds data of 620 at FIG. 6A) (e.g., while maintaining display of asecond set of content of the one or more complications). In someembodiments, the first set of content of the one or more complicationsthat were displayed in the first mode cease to be displayed as a resultof transitioning to the second mode.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes removing (e.g., ceasing todisplay) at least a portion of a background (e.g., solid backgroundcolor, a background image; 658) from the display. In some embodiments,one or more backgrounds that were displayed in the first mode cease tobe displayed as a result of transitioning to the second mode.

In some embodiments, the background has a first visual characteristic(e.g., a first color) and wherein transitioning the electronic devicefrom the first mode (e.g., a higher power consumption mode) to thesecond mode (e.g., a lower power consumption mode) includes displaying,at a location corresponding to the removed portion of background (e.g.,658), a third graphical object (e.g., 659) (e.g., an outline having thesame shape as a the background; an unfilled geometric shape) having thefirst visual characteristic.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes reducing a precision (e.g., adegree of accuracy or exactness of a value (e.g., a time value, ameasurement value)) of displayed information (e.g., of the timeindicator; 610 at FIGS. 6A and 6C; 620 at FIGS. 6A and 6C). In someembodiments, the first user interface includes display of a firstinformation with first precision and the second user interface includesdisplay of the first information with second precision less than thefirst precision. Reducing the precision of displayed information enablesthe device to perform less operations to determine the displayedinformation and/or allows the display to display less information (e.g.,don't display seconds when displaying time), thereby providing the userwith valuable feedback while reducing processing usage and/or reducingdisplay brightness (e.g., turning off pixels that would otherwise beused to display the additional precision information). Reducingprocessing usage and reducing the display brightness reduces power usageand improves the battery life of the device.

In some embodiments, reducing a precision of displayed informationincludes reducing a precision of a time-based visual element by ceasingto display seconds information (e.g., a seconds counter, a seconds hand;610 at FIGS. 6A and 6C; 620 at FIGS. 6A and 6C) of the time-based visualelement (e.g., while continuing to display minutes and/or hoursinformation of the time-based visual element).

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes removing (e.g., ceasing todisplay) a respective type of information (e.g., potentially sensitiveinformation such as calendar information, physical activity information;information deemed to be personal information (e.g., information that isparticular to a user of the electronic device)) from the display whilecontinuing to display information that is not of the respective type ofinformation (e.g., time information, weather information; information isnon-personal; information that is the same for different users; eventdescription of 614 at FIGS. 6A and 6C).

In some embodiments, subsequent to (e.g., in response to) detecting thatthe electronic device has met criteria for transitioning from the firstmode to a second mode and in accordance with a determination that aninformation suppression setting is enabled (e.g., 640), the electronicdevice (e.g., 600) removes (e.g., ceasing to display) information of arespective type of information (e.g., potentially sensitive informationsuch as calendar information, physical activity information; informationdeemed to be personal information (e.g., information that is particularto a user of the electronic device)) while continuing to displayinformation that is not of the respective type of information (e.g.,time information, weather information; 614 at FIG. 6C). In someembodiments, subsequent to (e.g., in response to) detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode and in accordance with a determination that theinformation suppression setting is not enabled, the electronic device(e.g., 600) continues to display the information of the respective typeof information and the information that is not of the respective type ofinformation (e.g., time information, weather information; information isnon-personal; information that is the same for different users).

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes reducing the display size of oneor more visual elements (614, 616, 618, 620, 624, 626, and 628 of FIG.6C) (e.g., second time indicator is smaller than first time indicatorand/or second graphical object is smaller than first graphical object).In some embodiments, the center position of the second time indicator isthe same as the center position of the first time indicator. In someembodiments, the center position of the second graphical object is thesame as the center of the first graphical object. Reducing the size ofvisual elements on the display enables the device to conserve batterypower by avoiding energizing the pixels that the visual elementspreviously used (e.g., by turning off the pixels not required to displaythe smaller version of the visual element). Avoiding energizing pixelsof the display reduces the display brightness. Reducing the displaybrightness reduces power usage and improves the battery life of thedevice.

In some embodiments, prior to displaying the first user interface (e.g.,a clock face of a smart watch), the electronic device (e.g., 600)detects a user input, wherein displaying the first user interface isbased on (e.g., is in response to) detecting the user input. In someembodiments, the criteria for transitioning from the first mode to thesecond mode includes a first criterion, wherein: in accordance with adetermination that the user input is of a first type (e.g., tap or othertouch gesture on a touch-sensitive surface of the electronic device),the first criterion is met based on a first amount of time havingelapsed (e.g., the first amount of time having elapsed after detectingthe user input, the first amount of time having elapsed after detectingthe last user input while in the first mode); and in accordance with adetermination that the user input is of a second type (e.g., wrist raisegesture detected by one or more motion sensors), the first criterion ismet based on a second amount of time having elapsed (e.g., the secondamount of time having elapsed after detecting the user input, the secondamount of time having elapsed after detecting the last user input whilein the first mode), the second time being different from the first time.In some embodiments, the electronic device stays in the first mode fordifferent amounts of time (e.g., by transitioning to the second modeafter varying amounts of time) based on the time of user input thatcaused the electronic device to enter the first mode. In some examples,the electronic device stays in the first mode for a longer duration whena touch gesture on the electronic device's touch-sensitive surfacecauses the electronic device to transition to the first mode because thetouch gesture is likely to be intentional input and the electronicdevice stays in the first mode for a shorter duration when amotion-based gesture (e.g., wrist raise) causes the electronic device totransition to the first mode because the motion-based gesture is lesslikely to be intentional input.

In some embodiments, the first user interface includes display of ananimation that includes a first animation portion and a second animationportion (e.g., 648 at FIG. 6Q) and the second user interface includesdisplay of the first animation portion without displaying the secondanimation portion (e.g., 648 at FIG. 6R). In some embodiments, the watchface includes an animated aspect that is abbreviated when in the secondmode. Selecting a different point for an animation to end enables thedisplay to show different content (different part of the animation)during different playbacks of the animation, thereby avoiding the samecontent (e.g., the ending frame of the animation) from being displayedon the display for extended periods of time (e.g., after the animationhas stopped), thereby reducing the likelihood of the negative effects,such as display burn-in, of displaying the same content at the samelocation on the display.

In some embodiments, while in the second mode, the electronic device(e.g., 600) detects (e.g., a beginning of) a second user input (e.g.,632-2, 632-6, 632-7, 632-8) (e.g., a touch gesture input on atouch-sensitive surface of the electronic device, a rotation of arotatable input mechanism of the electronic device). In response todetecting the second user input, the electronic device (e.g., 600)transitions from the second mode to the first mode, including replacingdisplay of the second user interface with display of the first userinterface (e.g., FIGS. 6D-6H).

In some embodiments, the electronic device includes a rotatable inputmechanism (e.g., 604) (e.g., a physical crown that is rotatable relativeto a display and/or housing of the electronic device). The second userinput is rotation of the rotatable input mechanism (e.g., 632-2). Insome embodiments, replacing display of the second user interface (e.g.,608-3, 608-6) with display of the first user interface (e.g., 608-1,608-8) occurs in conjunction with detecting rotation (e.g., 632-2,632-6, 632-7, 632-8) of the rotatable input mechanism (e.g., thetransition from the second user interface to the first user interfaceoccurs over time where an incremental rotation of the rotatable inputmechanism results in a corresponding incremental transition from thesecond user interface to the first user interface). In some embodiments,rotating the crown cases the visual elements in the second userinterface to transition to the corresponding visual elements of thefirst user interface (e.g., in size, shape, location, brightness).

In some embodiments, the electronic device includes a rotatable inputmechanism (e.g., 606) (e.g., a physical crown that is rotatable relativeto a display and/or housing of the electronic device). While in thesecond mode, the electronic device (e.g., 600) detects (e.g., abeginning of) a third user input (e.g., 632-7 and 632-8) (e.g., rotationof a rotatable input mechanism of the electronic device). In response todetecting the second user input, the electronic device (e.g., 600)transitions from the second mode to the first mode and increasing thebrightness of the display (e.g., 602 at FIGS. 6F-6H). In someembodiments, the transition from the second mode to the first modeoccurs in response to an initial portion of the input and the first modeis initially displayed in a dimmed state and the dimmed state isgradually brightened as the input continues (e.g., a magnitude ofrotation of the rotatable input element determines an amount of changein brightness of the user interface, and a direction of rotation of therotatable input mechanism determines whether a brightness of the userinterface is increased or decreased).

In some embodiments, the first time indicator (e.g., 610 at FIG. 6S)includes a gradient that indicates a measure of time (e.g., 652, 654)(e.g., seconds, minutes, hours) and wherein the second time indicator(e.g., 610 at FIG. 6T) does not include a gradient that indicates themeasure of time (or that indicates any measures of time).

In some embodiments, the first time indicator includes a first gradient(e.g., 650 at FIG. 6S) (e.g., a color gradient that varies based ondirection from an origin; the color gradient has the first color at afirst edge of the gradient, which is located along a first directionfrom the origin, and the second color at a second edge of the gradient,which is located along a second direction from the origin. The colorchanges gradually (e.g., smoothly or in increments) with angle from thefirst color to the second color. The term “color” refers to differenthues, tones, shades, tints, including but is not limited to, black,white, and gray.). The first gradient transitions from a first color toa second color and that indicates a measure of time (e.g., seconds,minutes, hours). The second time indicator (e.g., 650 at FIG. 6T)includes a second gradient that transitions from a third color to thesecond color that indicates the measure of time, wherein the third coloris different from the first color. In some embodiments, the firstgradient transitions from a first non-black color to a second non-blackcolor and the second gradient transitions from a third non-block color(e.g., same as the first non-black color) to a black color. By replacingthe second non-black color with a black color in the second gradient,the second gradient is darker (overall) than the first gradient, therebyconserving power for display of the second gradient as compared to thefirst gradient.

In some embodiments, the electronic device includes a touch-sensitivesurface (e.g., 602). The electronic device (e.g., 600) detects, usingthe touch-sensitive surface, a tap input (e.g., 632-5, 632-9) at alocation corresponding to a displayed complication (e.g., 628) (e.g.,that includes weather information, calendar information, or physicalactivity information) associated with an application (e.g., thecomplication displays information received from the application). Inresponse to detecting the tap input: in accordance with a determinationthat the electronic device is in the first mode, the electronic device(e.g., 600) replaces display of the first indication of time withdisplay of the application (e.g., 608-9) (e.g., without changing modes);and in accordance with a determination that the electronic device is inthe second mode, the electronic device (e.g., 600) transitions from thesecond mode to the first mode without replacing display of the secondindication of time with display of the application (e.g., FIGS. 6D-6H).In some embodiments, in accordance with a determination that theelectronic device is in the second mode, the electronic device replacesdisplay of the second indication of time with display of the firstindication of time.

In some embodiments, the electronic device (e.g., 600) detects (e.g.,using a touch-sensitive surface) a swipe gesture input (e.g., 632-1,632-11). In response to detecting the swipe gesture input: in accordancewith a determination that the electronic device is in the first mode,the electronic device (e.g., 600) performs an operation (e.g.,displaying 608-11) (e.g., that corresponds to the swipe gesture input);and in accordance with a determination that the electronic device is inthe second mode, the electronic device (e.g., 600) maintains theelectronic device in the second mode without performing the operation(e.g., displaying 608-4). In some embodiments, in accordance with adetermination that the electronic device is in the first mode, thetechnique maintains the electronic device in the first mode. In someembodiments, the operation includes one or more of: displaying one ormore received notifications, changing a clock face of the electronicdevice, displaying one or more affordances for configuring theelectronic device. In some embodiments, the electronic device ignores,disregards, and/or does not act upon swipe gesture inputs when theelectronic device is in the second mode. Avoiding performing operationsreducing the processing that the device is required to do, therebyreducing the power usage of the device and improving the battery life ofthe device.

In some embodiments, the electronic device (e.g., 600) detects (e.g.,using a touch-sensitive surface) a swipe gesture input (e.g., 632-1). Inresponse to detecting the swipe gesture input: in accordance with adetermination that the electronic device is in the first mode, theelectronic device (e.g., 600) performs an operation while maintainingthe electronic device in the first mode (e.g., that corresponds to theswipe gesture input); and in accordance with a determination that theelectronic device is in the second mode, the electronic device (e.g.,600) performs the operation (e.g., displaying 608-11) (and, optionally,transitioning the electronic device to the first mode). In someembodiments, in accordance with a determination that the electronicdevice is in the first mode, the technique maintains the electronicdevice in the first mode. In some embodiments, the operation includesone or more of: displaying one or more received notifications, changinga clock face of the electronic device, displaying one or moreaffordances for configuring the electronic device.

In some embodiments, while the electronic device is in the first modeand displaying the first user interface (e.g., 608-1) (e.g., prior todetecting that the electronic device has met criteria for transitioningfrom the first mode to a second mode; after detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode) and while the electronic device is connected (e.g.,via a wire; wireless) to an external power source (e.g., a charger;636), the electronic device (e.g., 600) detects that the electronicdevice has met criteria for transitioning from the first mode to a thirdmode (e.g., description of FIGS. 6A-6B). In response to detecting thatthe electronic device has met the criteria for transitioning from thefirst mode to the third mode (e.g., criteria for turning off thedisplay), the electronic device (e.g., 600) ceases to display the firsttime indicator and the first graphical object without displaying thesecond time indicator and second graphical object (e.g., 602 in FIG. 6L)(e.g., turning off the display, black out the display) (e.g., withoutentering the second mode).

In some embodiments, while the electronic device (e.g., 600) is in thefirst mode and displaying the first user interface (e.g., prior todetecting that the electronic device has met criteria for transitioningfrom the first mode to a second mode; after detecting that theelectronic device has met criteria for transitioning from the first modeto a second mode), the electronic device (e.g., 600) detects a request(e.g., a set of one or more user inputs that enables a fourth mode) totransition the electronic device from the first mode to a fourth mode(e.g., a theater mode; a mode in which the display is inactive and onlyreactivates (e.g., re-enters the first mode) based on selected userinput (e.g., does not activate based on certain inputs that wouldactivate the display (e.g., re-enters the first mode) while in thesecond mode; a mode that also involves suppressing notifications)). Inresponse to detecting the request to transition the electronic devicefrom the first mode to the fourth mode, the electronic device (e.g.,600) ceases to display the first time indicator and the first graphicalobject without displaying the second time indicator and second graphicalobject (e.g., 602 in FIG. 6L) (e.g., turning off the display, black outthe display) (e.g., without entering the second mode).

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, methods 900, 1100, 1300, 1500,1700, and 1900 optionally include one or more of the characteristics ofthe various methods described above with reference to method 700. Forexample, the first mode is the same mode throughout these methods andthe second mode is the same mode throughout these methods. For brevity,these details are not repeated below.

FIGS. 8A-8M illustrate exemplary techniques for displaying a userinterface, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 9.

FIGS. 8A-8M illustrate exemplary techniques for displaying userinterfaces, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 9. In particular, FIGS. 8A-8M illustratetechniques for managing display usage by altering one or more aspects(e.g., visual characteristics) of a displayed user interface upondetermining that the device has met a mode-transition criteria (e.g., asdescribed above with respect to FIGS. 6A-6B).

FIGS. 8A-8D illustrate changes made to corresponding elements of adisplayed clock face user interface as device 600 transitions from astandard display mode to a low power display mode. In particular, thesequence of displayed clock face user interfaces illustrated in FIGS.8A-8D are displayed by device 600 at progressively lower brightnessvalues while graphical elements (e.g., affordances, complication,indicators, etc.) resize and dim at different times throughout the modetransition.

FIG. 8A depicts device 600 displaying clock face user interface 808-1(e.g., a higher power consumption user interface). In some embodiments,clock face user interface 808-1 corresponds to or is the same as clockface user interface 608-13.

FIG. 8B illustrates device 600 after failing to detect user input for apredetermined period of time (e.g., a mode-transition criteria has beenmet and in response, device 600 has initiated a transition from standarddisplay mode to low power display mode). At FIG. 8B, while in a modetransitional state, device 600 displays clock face user interface 808-2on display 602 (e.g., device 600 displays a transitional interface).Clock face user interface 808-2 is a frame of an animation (e.g., asequence of frames or images) illustrating clock face user interface808-1 (e.g., a higher power consumption user interface) visuallymorphing into a corresponding low power consumption user interface(e.g., clock face user interface 808-4 as depicted in FIG. 8D).

As depicted in FIG. 8B, device 600 displays digital indication of time842, date indicator 844, and timer affordance 820 in clock face userinterface 808-2 at reduced sizes and brightness levels compared to theirrespective appearance in clock face user interface 808-1 (e.g.,corresponding outlines representing the size of elements in clock faceuser interface 808-1 while device is in standard display mode). Asdepicted in FIG. 8B, digital indication of time 842, date indicator 844,and timer affordance 820 have shrunk inward about their respectivecenter points (e.g., the center of each of these elements remains in thesame position relative to the edges of display 602 in both FIG. 8A andFIG. 8B), thereby increasing the distance between elements in clock faceuser interface 808-8. Additionally, timer affordance 620 is displayed bydevice 600 without seconds data.

FIG. 8C depicts device 600 at a time after clock face user interface808-2 has been displayed. At FIG. 8C, while in a mode transitionalstate, device 600 displays clock face user interface 808-3 on display602 (e.g., device 600 displays an additional transitional interface). Asdepicted in FIG. 8C, device 600 displays calendar affordance 846 at areduced size and brightness level compared its respective appearance inclock face user interface 808-2. As depicted in FIG. 8C, calendaraffordance 846 has shrunk inward (e.g., about its own center).

FIG. 8D illustrates device 600 at a time after clock face user interface808-3 has been displayed (e.g., after device 600 has completelytransitioned to low power display mode). At FIG. 8D, while operating inlow power display mode, device 600 displays clock face user interface808-4 (e.g., a lower power consumption user interface) on display 602.In some embodiments, clock face user interface 808-4 corresponds to oris the same as clock face user interface 608-14. Clock face userinterface 808-4 (e.g., a lower power consumption user interface) isdisplayed at a lower brightness level than clock face user interface808-1 (e.g., a higher power consumption user interface). As depicted inFIG. 8D, workout affordance 828, compass affordance 818, and world clockaffordance 816 have shrunk inward (e.g., about their own centers) anddimmed relative to their appearance in clock face user interface 808-3.Additionally, compass affordance 620 is displayed by device 600 withoutseconds data.

At FIG. 8D, while operating in low power display mode, device 600detects user input 832-1 (e.g., a tap gesture on display 602). Inresponse to detecting user input 832-1, device 600 initiates atransition back to the standard display mode, by first displaying anemphasis animation visually indicating to the user that a modetransition has been initiated (e.g., clock face user interface 808-5 asdepicted in FIG. 8E illustrates a frame of an exemplary emphasisanimation). As depicted in FIG. 8E, digital indication of time 842, aswell as each displayed affordance, is displayed in a further dimmed andshrunken state prior to device 600 transitioning back to low powerdisplay mode.

FIGS. 8F-8H depict device 600 as it transitions from low power displaymode to standard display mode (e.g., device 600 performs a reversal ofthe transition sequence described above with respect to FIGS. 8A-8D). Insome embodiments, the transition back to standard display mode occurs atdifferent rates depending on the mode-transition criteria that initiatedthe reversal (e.g., faster if device 600 detected a wrist raise gestureand slower if device detected a tap gesture).

In some embodiments, as depicted in FIG. 8I, rather than shrinking inplace (e.g., inward), one or more elements displayed in clock face userinterface 808-1 may instead shrink in a directional manner. For example,as depicted in FIG. 8I, upon transitioning to low power display mode,digital indication of time 842, date indicator 844, timer affordance820, workout affordance 828, compass affordance 818, and world clockaffordance 816 have shrunk toward the center of display 602 therebytranslating their respective center points away from the edges ofdisplay 602. In some embodiments, elements in clock face user interface808-9 scale within the area they occupied while in standard display mode(e.g., as indicated by respective outlines). Additionally, as depictedin FIG. 8I, the shrinking of a clock face user interface element upontransition to low power display mode can vary (e.g., in direction ormagnitude) based a time associated with the mode-transition (e.g., basedin part on date, day, month, week, etc.).

FIGS. 8J-8L depict another example of device 600 transitioning fromstandard display mode to low power display mode and the correspondingchanges to the clock face user interface displayed by device 600. AtFIG. 8J, while in a standard display mode, device 600 displays clockface user interface 808-10 (e.g., a higher power consumption userinterface). In some embodiments, clock face user interface 808-10corresponds to or is the same as clock face user interface 608-1. Asillustrated by FIGS. 8K and 8L, device 600 first shrinks outeraffordances (e.g., closer to the edge of display 602) and subsequentlyshrinks the interior affordances (e.g., affordances closer to the centerto display 602) as device 600 transitions to low power display mode.FIG. 8M depicts device 600, while operating in low power display mode ata later time (e.g., date, day, month, week, etc.). As depicted in FIG.8M, the shrinking of a clock face user interface element upon transitionto low power mode can vary. For example, the shrinking can bedirectional (e.g., as described above with respect to FIG. 8I), appliedin a non-uniform manner (e.g., outer affordances shrink more thaninterior affordances), or of different magnitudes.

FIG. 9 is a flow diagram illustrating a method for managing displayusage using an electronic device in accordance with some embodiments.Method 900 is performed at a device (e.g., 100, 300, 500, 600, a smartwatch, a smart phone, a tablet computer) with a display. Some operationsin method 900 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

While the electronic (e.g., 600) device is in a first mode (e.g., ahigher power consumption mode), the electronic device (e.g., 600)displays (902) on the display (e.g., 602), a first user interface (e.g.,a clock face of a smart watch) including a first time indicator (904)and a first graphical object (906).

The first time indicator (904) indicates a current time (e.g., 842 atFIG. 8A) (e.g., a clock hand (hour, minute, second hand); a digital timenumeral (hour, minute, second numerals) and is displayed at a firstsize. The first graphical object (906) (e.g., 816, 818, 820, 828, 846,and 844 at FIG. 8A) (e.g., an affordance; a complication) is displayedat a second size.

The electronic device (e.g., 600) detects (908) that the electronicdevice has met criteria for transitioning from the first mode to asecond mode. In response to detecting that the electronic device has metthe criteria for transitioning from the first mode to the second mode,electronic device (e.g., 600) transitions (910) the electronic devicefrom the first mode (e.g., a higher power consumption mode) to thesecond mode (e.g., a lower power consumption mode).

While the electronic device is in the second mode, electronic device(e.g., 600) displays (912) on the display, a second user interface(e.g., 808-10) including: a second time indicator (914) and a secondgraphical object (916).

The second time indicator (914) (e.g., 842 at FIG. 8D) indicates thecurrent time (e.g., an analog clock hand (hour, minute, second hand); adigital clock numeral (hour, minute, second numerals)). The second timeindicator is displayed at a third size that is smaller than the firstsize, at which the first time indicator was previously displayed.

The second graphical object (916) (e.g., 816, 818, 820, 828, 846, and844 at FIG. 8D) corresponds to the first graphical object (e.g., anon-interactive version of the first graphical object; a visuallydistinct graphical object representing to the same application as thefirst graphical object; a graphical object including a subset of thedata included in the first graphical object (only mm remaining ratherthan mm:ss remaining)). The second graphical object is displayed at afourth size that is smaller than the second size, at which the firstgraphical object was previously displayed. As discussed above in greaterdetail, the first mode and the second mode are different modes in whichthe electronic device can operate. Reducing the size of visual elementson the display enables the device to conserve battery power by avoidingenergizing the pixels that the visual elements previously used (e.g., byturning off the pixels not required to display the smaller version ofthe visual element). Avoiding energizing pixels of the display reducesthe display brightness, which reduces power usage and improves thebattery life of the device.

In some embodiments, the first time indicator (e.g., 842 at FIG. 8A) andthe first graphical object (e.g., 820 at FIG. 8A) are spaced apart by afirst distance in the first user interface (e.g., 808-1). In someembodiments, the second time indicator (e.g., 842 at FIG. 8D) and thesecond graphical object (e.g., 820 at FIG. 8A) are spaced apart by asecond distance in the second user interface (e.g., 808-10). In someembodiments, the second distance is greater than the first distance. Insome embodiments, the distance between the time indicator and thegraphical object increases as a result of transitioning the electronicdevice from the first mode (e.g., a higher power consumption mode) tothe second mode (e.g., a lower power consumption mode).

In some embodiments, while the electronic device is in the first mode(e.g., a higher power consumption mode), the electronic device (e.g.,600) displays on the display in the first user interface (e.g., a clockface of a smart watch), a third graphical object (e.g., an affordance; acomplication; 828 at FIG. 8A) that is displayed at a fifth size. Whilethe electronic device is in the second mode, the electronic device(e.g., 600) displays on the display in the second user interface, afourth graphical object (e.g., 828 at FIG. 8D) corresponding to thethird graphical object (e.g., a non-interactive version of the thirdgraphical object; a visually distinct graphical object representing tothe same application as the third graphical object; a graphical objectincluding a subset of the data included in the third graphical object(only mm remaining rather than mm:ss remaining)). The fourth graphicalobject is displayed at a sixth size that is smaller than the fifth size,at which the third graphical object was previously displayed. Reducingthe size of visual elements on the display enables the device toconserve battery power by avoiding energizing the pixels that the visualelements previously used (e.g., by turning off the pixels not requiredto display the smaller version of the visual element). Avoidingenergizing pixels of the display reduces the display brightness, whichreduces power usage and improves the battery life of the device.

In some embodiments, the first graphical object (e.g., 820 at FIG. 8A)and the third graphical object (e.g., 828 at FIG. 8A) are spaced apart(e.g., based on the closet points of each object to the other object orbased on the centers of the objects or some other measurement) by athird distance in the first user interface (e.g., 808-1). In someembodiments, the second graphical object (e.g., 820 at FIG. 8D) and thefourth graphical object (e.g., 828 at FIG. 8D) are spaced apart by afourth distance in the second user interface. In some embodiments, thefourth distance is greater than the third distance. In some embodiments,the distance between the complications increases as a result oftransitioning the electronic device from the first mode (e.g., a higherpower consumption mode) to the second mode (e.g., a lower powerconsumption mode).

In some embodiments, the first time indicator (e.g., 842 at FIG. 8A) andthe second time indicator (e.g., 842 at FIG. 8I) are digital timeindicators and wherein a center of the second time indicator is closerto the center of the display as compared to a center of the first timeindicator. In some embodiments, a combination of the first timeindicator (e.g., 842 at FIG. 8A) and the second graphical object (e.g.,844 at FIG. 8A) have a combined center. In some embodiments, acombination of the second time indicator (e.g., 842 at FIG. 8D) and thesecond graphical object (e.g., 844 at FIG. 8D) have the same combinedcenter. In some embodiments, the time indicator and the graphical objectare grouped together such that they scale in size together and maintaina center with respect to the group when scaled. Maintaining a combinedcenter of graphical elements enables the device to display the graphicalelements at the same location, thereby providing the user with improvedvisual feedback such that the user can easily identify that the samecontent is being displayed in a different form factor. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, a combination (e.g., a group) of the firstgraphical object (e.g., 816, 818, 828 at FIG. 8A) and the secondgraphical object (e.g., 816, 818, 828 at FIG. 8A) have a combinedcenter. In some embodiments, a combination of the third graphical object(e.g., 816, 818, 828 at FIG. 8D) and the fourth graphical object (e.g.,816, 818, 828 at FIG. 8D) have the same combined center. In someembodiments, the graphical objects are grouped together such that theyscale in size together and maintain a center with respect to the groupwhen scaled.

In some embodiments, the first time indicator is displayed at a firstlocation on the display as part of the first user interface while in thefirst mode. In some embodiments, the first graphical object (e.g., 816,818, 820, 828, 846, and 844 at FIG. 8A) (e.g., an affordance; acomplication) is displayed at a second location on the display as partof the first user interface while in the first mode. In someembodiments, the second time indicator is displayed at a third locationon the display as part of the second user interface while in the secondmode, the third location being different from the first location. Insome embodiments, the second graphical object (e.g., 816, 818, 820, 828,846, and 844 at FIG. 8D) (e.g., an affordance; a complication) isdisplayed at a fourth location on the display as part of the second userinterface while in the second mode, the fourth location being differentfrom the second location.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second modeincludes: a first animation (e.g., 808-1 and 808-2) transitioning thefirst time indicator (e.g., 842 at FIG. 8A) to the second time indicator(e.g., 842 at FIG. 8B), and a second animation (e.g., 808-2 and 808-3)transitioning the first graphical object (e.g., 846 at FIG. 8B) to thesecond graphical object (e.g., 846 at FIG. 8C). The first animationbegins before the second animation begins. In some embodiments, thefirst animation ends before the second animation begins. In someembodiments, a third animation transitions the third graphical object tothe fourth graphical object. In some embodiments, the second animationbegins before the third animation. In some embodiments, the secondanimation ends before the third animation begins. Displaying animationsat different starting times for different graphical elements providesthe user with improved visual feedback by enabling the user toindividually appreciate how each graphical element is changing, therebybetter understanding which element in the second mode corresponds towhich element from the first mode. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the first graphical object (e.g., 846 at FIG. 8A)is displayed closer to the center of the display in the first userinterface than the third graphical object (e.g., 816, 818, and 828 atFIG. 8A) in the first user interface. In some embodiments, transitioningthe electronic device from the first mode (e.g., a higher powerconsumption mode) to the second mode includes: a second animation (e.g.,transition from 808-2 to 808-3) transitioning the first graphical objectto the second graphical object, and a third animation (e.g., transitionfrom 808-3 to 808-4) transitioning the third graphical object to thefourth graphical object. In some embodiments, the second animationbegins before the third animation begins. In some embodiments, thesecond animation ends before the third animation begins. In someembodiments, graphical objects (such as complications) are resizedand/or moved on the display using animations when the electronic devicetransitions from the first mode to the second mode. In some embodiments,graphical objects further from the center of the display are animated toresize and/or move before objects closer to the center of the display.Displaying animations at different starting times for differentgraphical elements provides the user with improved visual feedback byenabling the user to individually appreciate how each graphical elementis changing, thereby better understanding which element in the secondmode corresponds to which element from the first mode. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the first graphical object (e.g., 820 at FIG. 8A)is displayed is closer to a first edge (e.g., the bottom edge) of thedisplay in the first user interface than the third graphical object(e.g., 816 at FIG. 8A) in the first user interface. In some embodiments,transitioning the electronic device from the first mode (e.g., a higherpower consumption mode) to the second mode includes: a second animation(e.g., transition from 808-1 to 808-2) transitioning the first graphicalobject to the second graphical object, and a third animation (e.g.,transition from 808-2 to 808-3) transitioning the third graphical objectto the fourth graphical object. In some embodiments, the secondanimation begins before the third animation begins. In some embodiments,the second animation ends before the third animation begins. In someembodiments, graphical objects (such as complications) are resizedand/or moved on the display using animations when the electronic devicetransitions from the first mode to the second mode. In some embodiments,graphical objects displayed closer to the bottom of the display areanimated to resize and/or move before objects displayed further from thebottom edge of the display. Displaying animations at different startingtimes for different graphical elements provides the user with improvedvisual feedback by enabling the user to individually appreciate how eachgraphical element is changing, thereby better understanding whichelement in the second mode corresponds to which element from the firstmode. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves the battery lifeof the device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first time indicator (e.g., 810 at FIG. 8K) andthe first graphical object (e.g., 820, 822, 828 at FIG. 8K) are spacedapart by a first distance in the first user interface (e.g., 810) (e.g.,based on the closet points of each object to the other object or basedon the centers of the objects or some other measurement). In someembodiments, the second time indicator (e.g., 810 at FIG. 8M) and thesecond graphical object (e.g., 820, 822, 828 at FIG. 8M) are spacedapart by a second distance in the second user interface (e.g., 810)(e.g., based on the closet points of each object to the other object orbased on the centers of the objects or some other measurement). In someembodiments, the first distance is greater than the second distance. Insome embodiments, the distance between the time indicator and thegraphical object decreases as a result of transitioning the electronicdevice from the first mode (e.g., a higher power consumption mode) tothe second mode (e.g., a lower power consumption mode).

In some embodiments, the fourth size is smaller than the second size bya first percentage (e.g., relative size of 846 in FIGS. 8A and 8D) andthe sixth size is smaller than the fifth size by a second percentage(e.g., relative size of 828 in FIGS. 8A and 8D) different from the firstpercentage. In some embodiments, the amount of scaling is different fordifferent elements. For example, the first graphical object may reducein size by 10% when transitioning to the second graphical object whilethe third graphical object may reduce in size by 50% (or 5%) whentransitioning to the fourth graphical object. Using different amounts ofscaling for different visual elements enables the device to conservemore power by reducing the size of less relevant visual elements (e.g.,less used, less important elements) by a larger degree then the size ofmore relevant visual elements (e.g., more frequently used, moreimportant elements). As a result, the device continues to provide theuser with feedback while reducing the size of visual elements, whichreduces display brightness and reduces power usage.

In some embodiments, the first graphical object (e.g., 820 at FIG. 8A)is displayed closer to the center of the display in the first userinterface (e.g., 808-1) than the third graphical object (e.g., 828 atFIG. 8A) in the first user interface. In some embodiments, transitioningthe electronic device from the first mode (e.g., a higher powerconsumption mode) to the second mode includes: a second animationtransitioning the first graphical object to the second graphical object,and a third animation transitioning the third graphical object to thefourth graphical object. The first percentage is less than the secondpercentage. In some embodiments, graphical elements (e.g.,complications) displayed further from the center of the display reducein size (e.g., as a percentage) more than graphical elements displayedcloser to the center of the display.

In some embodiments, the fourth size is smaller than the second size bya first percentage and the third size is smaller than the first size bya third percentage that is less than the first percentage (e.g.,relative size of 810 and 828 at FIGS. 8J and 8L). In some embodiments,the amount of scaling is different for different elements. For example,the first time indication may reduce in size by 20% when transitioningto the second time indication while the first graphical object mayreduce in size by more (e.g., 50%) when transitioning to the secondgraphical object. Using different amounts of scaling for differentvisual elements enables the device to conserve more power by reducingthe size of less relevant visual elements (e.g., watch complications) bya larger degree then the size of more relevant visual elements (e.g.,time indicator). As a result, the device continues to provide the userwith feedback (e.g., of the time and of the complications) whilereducing the size of visual elements, which reduces display brightnessand reduces power usage.

In some embodiments, while the electronic device is in the second modeand displaying, on the display, the second user interface including thesecond time indicator at the third size and the second graphical objectat the fourth size, the electronic device (e.g., 600) detects that theelectronic device has met criteria for transitioning from the secondmode to the first mode (e.g., detecting a user input on the display,detecting motion (e.g., motion indicative of a wrist-raise)). Inresponse to detecting that the electronic device has met the criteriafor transitioning from the second mode to the first mode, the electronicdevice (e.g., 600) transitions from the second mode to the first mode,including: animating, over a first amount of time, a transition of thesecond time indicator (e.g., 842 in FIGS. 8G and 8H) at the third sizeto the first time indicator at the first size, and animating, over asecond amount of time, a transition of the second graphical object(e.g., 846 in FIGS. 8F-G) at the fourth size to the first graphicalobject at the second size. In some embodiments, transitioning from thesecond mode to the first mode includes animating the transition from thesecond time indicator to the first time indicator and animating thetransition from the second graphical object to the first graphicalobject. In some embodiments, the first time and the second time are thesame amounts of time (e.g., they animate over the same amount of time).In some embodiments, the first time and the second time are differentamounts of time.

In some embodiments, transitioning from the first mode (e.g., a higherpower consumption mode) to the second mode (e.g., a lower powerconsumption mode) includes: animating, over a third amount of time, atransition of the first time indicator (e.g., 842 at FIG. 8D) at thefirst size to the second time indicator at the third size, andanimating, over a fourth amount of time, a transition of the firstgraphical object (e.g., 846 at FIG. 8D) at the second size to the secondgraphical object at the fourth size. In some embodiments, transitioningfrom the first mode to the second mode includes animating the transitionfrom the first time indicator to the second time indicator and animatingthe transition from the first graphical object to the second graphicalobject. In some embodiments, the third time and the fourth time are thesame amounts of time (e.g., they animate over the same amount of time).In some embodiments, the third time and the fourth time are differentamounts of time. In some embodiments, the third amount of time (e.g.,animation when transitioning from first mode to second mode) isdifferent from the first amount of time (e.g., animation whentransitioning from second mode to first mode). In some embodiments, thethird amount of time is the same as the fourth amount of time. In someembodiments, the third amount of time is different from the fourthamount of time. In some embodiments, the first amount of time (e.g.,transitioning from second mode to first mode) is less than the thirdamount of time (transitioning from first mode to second mode). In someembodiments, the second amount of time is less than the fourth amount oftime.

In some embodiments, transitioning from the second mode (e.g., a lowerpower consumption mode) to the first mode (e.g., a higher powerconsumption mode) includes: in accordance with a determination that theuser input (e.g., 832-1) is of a first type (e.g., tap or other touchgesture on a touch-sensitive surface of the electronic device), thefirst amount of time is a first predetermined period of time; and inaccordance with a determination that the user input is of a second type(e.g., wrist raise gesture detected by one or more motion sensors)different from the first type, the first amount of time is a secondpredetermined period of time that is different from the firstpredetermined period of time. In some embodiments, in accordance with adetermination that the user input is of the first type (e.g., tap orother touch gesture on a touch-sensitive surface of the electronicdevice), the second amount of time is the first predetermined period oftime, and in accordance with a determination that the user input is of asecond type (e.g., wrist raise gesture detected by one or more motionsensors), the second amount of time is the second predetermined periodof time. In some embodiments, the transition from the second mode to thefirst mode happens at different rates based on the type of input thatcauses the transition.

In some embodiments, transitioning from the second mode to the firstmode includes displaying an animation (e.g., 808-5) that visuallyaccentuates one or more visual differences between the second userinterface displayed in the second mode and the first user interfacedisplayed in the first mode.

In some embodiments, visually accentuating one or more visualdifferences between the second mode and the first mode includes:reducing the display size of the second time indicator (e.g., 842 atFIGS. 8D-8F) to a size that is smaller than the third size beforedisplaying the first time indicator at the first size; and reducing thedisplay size of the second graphical (e.g., 820 at FIGS. 8D-8F) objectto a size that is smaller than the fourth size before displaying thefirst graphical object at the second size. In some embodiments, thetechnique shrinks the graphical elements before enlarging them toaccentuate the visual difference (e.g., size) between the elements inthe two states.

In some embodiments, while the electronic device is in the first mode(e.g., a higher power consumption mode) and displaying the first userinterface (e.g., a clock face of a smart watch), the first timeindicator (e.g., an analog clock hand (hour, minute, second hand); adigital clock numeral (hour, minute, second numerals)) is displayed at afirst brightness level (e.g., average pixel luminance (APL), averagelumen output, total lumen output, average illuminance, or totalilluminance of the indicator on the display; brightness expressed innits, lux, or lumens) and the first graphical object (e.g., anaffordance; an affordance representing a first application; aninteractive graphical object; an affordance displayed as a complicationassociated with a clock face; a non-updating graphical element (rotationpoint of a clock hand; colon separating digital clock numerals)) isdisplayed at a second brightness level (e.g., a brightness level that isthe same as the first brightness level; a brightness level that isdifferent than the first brightness level). Thus, the first timeindicator is displayed at a first brightness level and the firstgraphical object is displayed at a second brightness level. In someembodiments, while the electronic device is in the second mode anddisplaying the second user interface, the second time indicator isdisplayed at a third brightness level that is lower than the firstbrightness level, at which the first time indicator was previouslydisplayed and the second graphical object corresponding to the firstgraphical object (e.g., a non-interactive version of the first graphicalobject; a visually distinct graphical object representing to the sameapplication as the first graphical object; a graphical object includinga subset of the data included in the first graphical object (only mmremaining rather than mm:ss remaining)) is displayed at a fourthbrightness level that is lower than the second brightness level, atwhich the first graphical object was previously displayed.

In some embodiments, visually accentuating one or more visualdifferences between the second mode and the first mode includes:reducing the brightness level of the second time indicator (e.g., 842 atFIG. 8E) to a brightness level that is less than the third brightnesslevel before displaying the first time indicator at the first brightnesslevel; and reducing the brightness level of the second graphical object(e.g., 820 at FIG. 8E) to a brightness level that is less than thefourth brightness level before displaying the first graphical object atthe second brightness level. In some embodiments, the technique reducesthe brightness of the graphical elements before brightening them toaccentuate the visual difference (e.g., brightness) between the elementsin the two states.

In some embodiments, the third size and fourth size are selected basedon one or more resizing criteria (e.g., 844 at FIG. 8I) that cause thesizes (and, optionally positions) of elements of the user interface tovary when the device enters the second mode on different occasions(e.g., 808-9 at FIG. 8I) (e.g., even though the sizes and/or positionsof corresponding elements of the user interface do not vary when thedevice enters the first mode on different occasions). In someembodiments, the graphical elements are reduced in size to various sizessuch that the reduced sizes are not the same each time the second userinterface is displayed in the second mode. In some embodiments, theresizing criteria are based on day of the week, hours of the time, monthof the year, and/or year. Selecting a different sizes for content to bedisplayed enables the display to show the content and avoid having thecontent be displayed on the display for extended periods of time (e.g.,after the animation has stopped) at the same size, thereby reducing thelikelihood of the negative effects, such as display burn-in, ofdisplaying the same content at the same location/size on the display.

In some embodiments, the resizing criteria (e.g., 844 at FIG. 8I) isbased on one or more of a current hour of the day, a current day of theweek, a current date of the month, a current month of year, and acurrent year (e.g., 808-9 at FIG. 8I). In some embodiments, the one ormore resizing criteria cause the sizes (and, optionally positions) ofelements of the user interface to vary between various states (e.g.,resize by 90% during a first hour, 91% during a second hour, 92% duringa third hour, 93% during a fourth hour; resize by 90% during a first dayof week, 91% during a second day of week, 92% during a third day ofweek, 93% during a fourth day of week). Selecting a different sizes forcontent to be displayed based on hour, day, date, month, and/or yearenables the display to show the content and avoid having the content bedisplayed on the display for extended periods of time (e.g., after theanimation has stopped) at the same size, thereby reducing the likelihoodof the negative effects, such as display burn-in, of displaying the samecontent at the same location/size on the display.

In some embodiments, the electronic device (e.g., 600) selects the thirdsize for the second time indicator (e.g., 842 at FIG. 8I) that isdifferent from a size at which the second time indicator was lastdisplayed as part of the second user interface while the electronicdevice was in the second mode. In some embodiments, the electronicdevice (e.g., 600) selects the fourth size for the second graphicalobject (e.g., 820 at FIG. 8I) that is different from a size at which thesecond graphical object was last displayed as part of the second userinterface while the electronic device was in the second mode. In someembodiments, each time that the electronic device transitions from thefirst mode to the second mode the electronic device display thegraphical elements at a size that is different from the last time thegraphical element was displayed in the second mode. Selecting adifferent sizes for content to be displayed enables the display to showthe content and avoid having the content be displayed on the display forextended periods of time (e.g., after the animation has stopped) at thesame size, thereby reducing the likelihood of the negative effects, suchas display burn-in, of displaying the same content at the samelocation/size on the display.

In some embodiments, a first display brightness (e.g., Average PixelLuminance (APL)) of the display (e.g., 602 displaying 808-1) whiledisplaying the second user interface while the electronic device is inthe second mode (e.g., a lower power consumption mode) is less than asecond display brightness (e.g., APL) of the display (e.g., 602displaying 808-4) while displaying the first user interface (e.g., aclock face of a smart watch) while the electronic device is in the firstmode (e.g., a higher power consumption mode). Thus, the overallbrightness of the display is reduced when displaying the second userinterface while the electronic device is in the second mode as comparedto displaying the first user interface while the electronic device is inthe first mode. Reducing the overall brightness of the display reducespower usage and improves the battery life of the device, while stillenabling the user to access the device.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9) are also applicable in an analogous manner tothe methods described above/below. For example, methods 700, 1100, 1300,1500, 1700, and 1900 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 900. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

FIGS. 10A-10I illustrate exemplary techniques for displaying userinterfaces, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 11A-11B. In particular, FIGS. 10A-10Fillustrate techniques for managing display usage by displaying distinctuser interfaces upon determining that the device has met amode-transition criteria (e.g., as described above with respect to FIGS.6A-6C) based in part on the level of ambient light detected in theenvironment surrounding the device.

FIGS. 10A-10D depict device 600 operating in a bright environment (e.g.,device 600 is in direct sunlight). FIGS. 10A-10C illustrate device 600transitioning from standard display mode to low power display mode, asdescribed above with respect to FIGS. 6A-6C. At FIG. 10A, device 600displays clock face user interface 1008-1 while in standard displaymode. In some embodiments, clock face user interface 1008-1 correspondsto or is the same as clock face user interface 608-1. At FIG. 10B,device 600 displays clock face user interface 1008-2, which represents aframe of an animation depicting clock face user interface 1008-1 (e.g.,a higher power consumption user interface for higher ambient lightconditions) visually morphing into clock face user interface 1008-3(e.g., a lower power consumption interface for higher ambient lightconditions).

As depicted in FIG. 10C, at the conclusion of the mode transition,device 600 displays clock face user interface 1008-3 (e.g., a lowerpower consumption user interface for higher ambient light conditions) ondisplay 602 at a lower brightness compared to the corresponding clockface user interface in standard display mode (e.g., user interface1008-1 as depicted in FIG. 10A). In some embodiments, clock face userinterface 1008-3 corresponds to or is the same as clock face userinterface 608-3. In some embodiments, displaying clock face userinterface 1008-3 on display 602 at a lower brightness level includesapplying a mask (e.g., alpha blending as described above in reference toFIGS. 6A-6X).

As depicted in FIG. 10C, clock face user interface 1008-3 includes dateaffordance 1014, world clock affordance 1016, compass affordance 1018,timer affordance 1020, moon affordance 1024, stopwatch affordance 1026,and workout affordance 1028, each displayed at a reduced brightness andsize relative to their appearance in standard power mode as depicted inFIG. 10A. Additionally, various elements in clock face user interface1008-3 have been removed or altered relative to their appearance instandard power mode as depicted in FIG. 10A (e.g., as described inreference to FIG. 6C above). For example, heart complication 1022 hasbeen removed, white portions of analog indication of time 1010 and worldclock 1016 have been replaced with darker colors (e.g., greys),directional information has been removed compass affordance 1018,portions of stopwatch affordance 1026 (e.g., interior fill) and timescale 1012 (e.g., tick marks) have been removed. In some embodiments,time scale 1012 tick marks are reduced in thickness.

Additionally, analog indication of time 1010 is displayed in a lowerbrightness relative to its appearance in standard power mode (e.g., asdepicted in FIG. 10A) but hasn't dimmed as much as other affordancesincluded in clock face user interface 1008-3. In some embodiments,analog indication time 1010 is further modified to be displayed in adifferent color (e.g., a color included in the background of clock faceuser interface 1008-1). In some embodiments, the clock hands of analogindication time 1010 are further modified to be displayed in a differentsize (e.g., thinner).

At FIG. 10C, device 600 detects user input 1032-1 (e.g., a tap gestureon display 602). In response to user input 1032-1, device 600 displaysuser interface 1008-4 as depicted in FIG. 10D (e.g., device 600transitions back to standard display mode as described with respect toFIGS. 6D-6H above). In some embodiments, the transition back to lowpower mode occurs as described above with respect to FIGS. 6D-6F andFIGS. 8D-8H (e.g., transition includes displaying a transitionalanimation or in some cases, an emphasis animation prior to displaying atransitional animation). FIG. 10D, depicts device 600, once againoperating in a bright environment while in standard display mode (e.g.,displaying a higher power consumption interface for higher ambient lightconditions). At FIG. 10D, device 600 displays clock face user interface1008-4. In some embodiments, clock face user interface 1008-4corresponds to or is the same as clock face user interface 608-1.

FIG. 10E depicts device 600 after detecting a reduction in environmentalbrightness while in standard display mode (e.g., a user wearing device600 walks into a dark movie theater, device 600 determines that adetected environmental brightness value is below a threshold value). Insome embodiments, device 600 determines an environmental brightnesslevel based on data detected at one or more sensors of device 600 (e.g.,a phototransistor, photodiode, or other light-sensing device).

In response to detecting the drop in environmental brightness, device600 displays clock face user interface 1008-5 as depicted in FIG. 10E(e.g., device 600 displays a higher power consumption interface forlower ambient light conditions). In FIG. 10E, device 600 display clockface user interface 1008-5 with a reduced brightness relative to thedisplayed brightness of clock face user interface 1008-4 in FIG. 10E. Insome embodiments, displaying clock face user interface 1008-5 on display602 at lower brightness level includes applying a mask (e.g., alphablending as described above in reference to FIGS. 6A-6X). As depicted inFIG. 10E, device 600 continues displaying elements corresponding tothose displayed in clock face user interface 1008-4, but at reducedbrightness levels (e.g., elements on the user interface have not shiftedor transformed, and contain the same content relative to thecorresponding elements depicted in the higher power consumptioninterface for higher ambient light condition of FIG. 10D).

FIG. 10F illustrates device 600 after determining that a mode changecriteria has been met while device 600 continues to occupy a low lightenvironment (e.g., a mode-transition criteria has been met and inresponse, device 600 has initiated a transition from standard displaymode to low power display mode). In some embodiments, device 600displays an animation depicting clock face user interface 1008-5 (e.g.,higher power consumption user interface for lower ambient lightconditions) visually morphing into clock face user interface 1008-6(e.g., lower power consumption user interface for lower ambient lightconditions).

As depicted in FIG. 10F, device 600 displays clock face user interface1008-6 on display 602 at a lower brightness level than both clock faceuser interface 1008-5 as depicted FIG. 10E (e.g., the higher powerconsumption user interface for low ambient light conditions displayed instandard display mode) and clock face user interface 1008-3 as depictedin FIG. 10C (e.g., the lower power consumption user interface for higherambient light conditions displayed in low power display mode). In someembodiments, displaying clock face user interface 1008-6 on display 602at the lower brightness level includes applying a mask (e.g., alphablending as described above in reference to FIGS. 6A-6X).

As depicted in FIG. 10F, clock face user interface 1008-6 only includesanalog indication of time 1010 and time scale 1020, however, each isdisplayed thinner in appearance relative to corresponding elements inFIGS. 10A-10E.

In some embodiments, device 600 first transitions from displaying clockface user interface 1008-1 (e.g., a higher power consumption userinterface for high ambient light conditions) to displaying clock faceuser interface 1008-3 (e.g. a lower power consumption user interface forhigh ambient light conditions), as described above with respects10A-10C, then subsequently transitions to displaying clock face userinterface 1008-6 (e.g., a lower power consumption user interface forlower ambient light conditions). In some embodiments, portions of analogindication of time 1010 remain brightly displayed (e.g., dimming ofhands is foregone, and hands white), when device 600 transitionsdirectly from displaying clock face user interface 1010-3 (e.g. a lowerpower consumption user interface for high ambient light conditions) todisplaying clock face user interface 1008-6 (a lower power consumptionuser interface for lower ambient light conditions).

In some embodiments, clock face user interface 1008-6 (e.g., lower powerconsumption user interface for lower ambient light conditions) includesworkout affordance 1028 displayed at the brightness level depicted inFIG. 10E (e.g., in clock face user interface 1008-6, the relativedifference in brightness between workout affordance 1028 and analogindication of time 1010 is greater than the relative difference inbrightness between workout affordance 1028 and analog indication of time1010, as depicted in clock face user interface 1008-1 of FIG. 10A). Insome embodiments, displaying clock face user interface 1008-3 involvesother content modifications relative to clock face user interface 1008-3or clock face user interface 1008-1 (e.g., removing content (e.g.,complications, affordances, or portions thereof), altering thecomposition or size of elements (e.g., color, saturation, size, etc.),and dimming elements at various levels, as describe in reference to FIG.10C).

FIGS. 10G-10I illustrate additional clock face user interfaces, inaccordance with some embodiments.

FIG. 10G depicts device 600 displaying clock face user interface 1008-7in standard display mode while in a high ambient light environment(e.g., device 600 displays a higher power consumption user interface forhigher ambient light conditions). In some embodiments, clock face userinterface 1008-7 corresponds to or is the same as clock face userinterface 608-13. In some embodiments, device 600 displays a dimmedversion of clock face user interface 1008-7, upon detecting lowerambient light conditions (e.g., as described above in reference to FIG.10E).

FIG. 10H depicts device 600 displaying clock face user interface 1008-8in low power display mode while in a bright environment (e.g., device600 displays a lower power consumption interface for higher ambientlight conditions). In some embodiments, clock face user interface 1008-8corresponds to or is the same as clock face user interface 608-14. Asdepicted in FIG. 10H, while operating in low power display mode, device600 displays digital indication of time 1042 in a dimmed state, but at ahigher brightness level relative to other displayed complications (e.g.,workout affordance 1042, compass affordance 1018, world clock affordance1016, and timer affordance 1012).

FIG. 10I depicts device 600 displaying clock face user interface 1008-9in low power display mode while in a low ambient light environment(e.g., device 600 displays a lower power consumption user interface forlower ambient conditions). In some embodiments, device 600 transitionsbetween these clock face user interfaces (e.g., 1008-6, 1008-7, 1008-9)as described above in reference to FIGS. 10A-10F.

FIGS. 11A-11B are a flow diagram illustrating a method for managingdisplay usage using an electronic device in accordance with someembodiments. Method 1100 is performed at a device (e.g., 100, 300, 500,600, a smart watch, a smart phone, a tablet computer) with a display andone or more sensors (e.g., ambient light sensor). Some operations inmethod 1100 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

While the electronic device (e.g., 600) is in a first mode (e.g., ahigher power consumption mode), the electronic device (e.g., 600)displays (1102) on the display (e.g., 602), a first user interface(e.g., 1008-1, 1008-7) (e.g., a clock face of a smart watch; a higherpower user interface) at a first display brightness level (e.g., averagepixel luminance (APL), average lumen output, total lumen output, averageilluminance, or total illuminance of the display; brightness expressedin nits, lux, or lumens). The first user interface includes: a firsttime indicator (1104) (e.g., 1010 at FIG. 10A) (e.g., an analog clockhand (hour, minute, second hand); a digital clock numeral (hour, minute,second numerals)); and a first graphical object (1106) (e.g., 1020 atFIG. 10A) (e.g., affordances; interactive graphical objects;complications representing applications; non-updating graphical elements(rotation point of a clock hand, colon separating digital clocknumerals, clock dial background, etc.)).

The electronic device (e.g., 600) receives (1108) data from the one ormore sensors (e.g., a value (digital, analog voltage) representingambient light measured at a sensor of the electronic device).

The electronic device (e.g., 600) detects (1110) that the electronicdevice has met criteria for transitioning from the first mode to asecond mode (e.g., one or more criteria that are indicative of reduceduser activity or reduced user interaction with the electronic device(e.g., determining reduced user activity (physical movement) for apredetermined period of time, determining a lack of user input for apredetermined period of time, detecting a predefined gesture). In someembodiments, detecting that the electronic device has met the criteriaincludes one or more of: receiving data from one or more sensors (e.g.,accelerometer, gyroscope, proximity sensor) corresponding to a usergesture (e.g., wrist-down, wrist-up, palm over display), receiving datafrom one or more sensors indicating user activity below a thresholdactivity level, determining a predetermined period of time has elapsewithout device receiving user input at one or more input devices (e.g.,touch-screen, rotatable input mechanism, depressible input mechanism).

In response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, the electronicdevice (e.g., 600) transitions (1112) the electronic device from thefirst mode (e.g., a higher power consumption mode) to the second mode(e.g., a lower power consumption mode). As discussed above in greaterdetail, the first mode and the second mode are different modes in whichthe electronic device can operate.

While (1114) the electronic device is in the second mode: in accordancewith a determination that the data from the one or more sensorscorresponds to a first environmental brightness level, the electronicdevice (e.g., 600) displays (1116) a second user interface (e.g.,1008-3; 1008-8) (e.g., lower power consumption interface for highambient light conditions) at a second display brightness level less thanthe first display brightness level (e.g., average pixel luminance (APL)of inactive interface is lower than APL of the active interface). Thesecond user interface includes: a second time indicator (1118) (e.g.,1010 at FIG. 10C) different from the first time indicator in one or morevisual characteristics other than brightness (e.g., position, size,color, hue, saturation, opacity, shape); and a second graphical object(1120) (e.g., 1020 at FIG. 10C) that corresponds to the first graphicalobject (e.g., differs from the first graphical object in one or morevisual characteristics that is other than brightness (position, size,color, hue, saturation, opacity, shape)).

While (1114) the electronic device is in the second mode: in accordancewith a determination that the data from the one or more sensorscorresponds to a second environmental brightness level lower than thefirst environmental brightness level, the electronic device (e.g., 600)displays (1122) a third user interface user interface (e.g., 1008-6)(e.g., a lower power consumption interface for low ambient lightconditions) at a third display brightness level lower than the seconddisplay brightness level (e.g., average pixel luminance (APL) of thelower power consumption interface for low ambient light conditions isless than the APL of the lower power consumption interface for highambient light conditions). The third user interface includes differentcontent (e.g., 1008-6) than the second user interface (e.g., the thirduser interface includes a third time indicator different from the secondtime indicator (e.g., the third time indicator differs from the secondtime indicator in one or more visual characteristics (size, color, hue,saturation, opacity, shape)); the second user interface includes one ormore graphical objects not included in the third user interface (e.g.,the second includes a seconds indicator (analog or digital) and thirduser interface does not include a seconds indicator); the third userinterface includes a subset of the graphical objects included in thesecond interface (e.g., second user interface includes hour ticks and aseconds scale, and third user interface includes hour ticks but does notinclude a seconds scale); the second user interface includes a greaterquantity of graphical objects than the third user interface (e.g.,second user interface includes twelve hour markers (e.g., 1-12) and thethird user interface includes four hour markers (e.g., 12, 3, 6, 9));the second user interface includes one or more affordances(complications) and the third user interface does not include at leastone of the one or more affordances).

In some embodiments, the electronic device (e.g., 600) detects that theelectronic device has not met criteria for transitioning from the firstmode to the second mode (e.g., prior to detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode). In response to detecting that the electronic device hasnot met the criteria for transitioning from the first mode to the secondmode: in accordance with a determination that second data from the oneor more sensors corresponds to a third environmental brightness level,the electronic device (e.g., 600) displays the first user interface(e.g., 1008-5) at a fourth display brightness level different from(e.g., less than) the first display brightness level withouttransitioning the electronic device from the first mode (e.g., a higherpower consumption mode) to the second mode (e.g., a lower powerconsumption mode) (e.g., maintain the electronic device in the firstmode and continue to display the same user interface but at a differentbrightness level). In some embodiments, in accordance with adetermination that the data from the one or more sensors corresponds toan environmental brightness level different from the third brightnesslevel, the electronic device continues to display the first userinterface at the first display brightness level and does not transitionthe electronic device from the first mode (e.g., a higher powerconsumption mode) to the second mode (e.g., a lower power consumptionmode) (e.g., maintain the electronic device in the first mode andcontinue to display the same user interface at the same brightnesslevel). Changing the brightness of the display based on environmentalbrightness allows the contents of the display to be more easily visiblein bright ambient light, thereby providing the user with improved visualfeedback, while reducing battery usage in reduced ambient lightenvironments. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device).Reducing the display brightness reduces power usage and improves thebattery life of the device.

In some embodiments, transitioning the electronic device from the firstmode (e.g., a higher power consumption mode) to the second mode (e.g., alower power consumption mode) includes changing the color of one or moreuser interface elements (e.g., 1010, 1014, 1016, 1018, 1020, 1024, 1026,1028) having a first color (e.g., white) to be a color other than thefirst color (e.g., a darker color). In some embodiments, the electronicdevice changes the color of one or more white user interface elements ofthe first user interface to a first color when displaying the seconduser interface and to a second color (different from the first color)when displaying the third user interface. Changing certain coloredelements (e.g., white-colored, lighter colored) to a different colorallows the device reduce the brightness of elements that moresignificantly affect battery consumption and to mitigate the negativeeffects of displaying bright content at the same location on thedisplay, such as display burn-in, while at the same time reducing thedisplay brightness, which reduces power usage and improves the batterylife of the device.

In some embodiments, the first graphical object (e.g., 1014, 1018, 1020,and 1026 at FIG. 10A) is a complication (e.g., a calendar complication;a complication that displays data received from an application, such asa calendar application) corresponding to a respective application andthat includes display of data received from the respective application.In some embodiments, the second graphical object (e.g., 1014, 1018,1020, and 1026 at FIG. 10C) corresponds to the respective applicationand does not include display of data from the respective application. Insome embodiments, the complication displays data received from therespective application while in the first mode, but does not receiveand/or display the data from the respective application while in thesecond mode, thereby reducing the electronic device's power consumption.In some embodiments, the electronic device displays (while in the secondmode) a tick or dash mark instead of the data to indicate that the datais not being displayed. Reducing the information displayed enables thedevice to conserve battery power by avoiding energizing the pixels thatthe content previously used (e.g., turning off the pixels) and byreducing the requirement for the device to process data to determine theinformation for display. Reducing processing needs reduces power andimproves battery life. Avoiding energizing pixels of the display reducesthe display brightness, thereby reducing power usage and improving thebattery life of the device.

In some embodiments, displaying the second user interface (e.g., 1008-3,1008-8) (e.g., lower power consumption interface for high ambient lightconditions) at the second display brightness level includes applying amask (e.g., a black mask, a gray mask; an overlay) to a display area. Insome embodiments, the electronic device applies a mask the display toreduce the brightness level of the display. In some embodiments,displaying the third user interface (e.g., lower power consumptioninterface for low ambient light conditions) at the third displaybrightness level includes applying a black (or gray, or other color)mask to a display area. Applying a mask, such as a black or gray mask,to a display area reduces the display brightness with which that area isdisplayed. Reducing the display brightness reduces power usage andimproves the battery life of the device.

In some embodiments, displaying the second user interface (e.g., 1008-3,1008-8) (e.g., lower power consumption interface for high ambient lightconditions) at the second display brightness level includes turning offone or more pixels (e.g., 1014, 1018, 1020, and 1026 at FIG. 10A) (e.g.,that were on in the first mode when displaying the first userinterface). In some embodiments, displaying the third user interface(e.g., lower power consumption interface for low ambient lightconditions) at the third display brightness level includes turning offone or more pixels (e.g., that were on in the first mode when displayingthe first user interface). Turning off one or more pixels enables thedevice to conserve battery power by avoiding energizing the pixels thatthe content previously used. Avoiding energizing pixels of the displayreduces the display brightness, which reduces power usage and improvesthe battery life of the device.

In some embodiments, the first graphical object (e.g., 1014, 1016, 1018,1020, 1024, 1026, and 1028 at FIG. 10A) corresponds to a respectiveapplication. In some embodiments, the second graphical object (e.g.,1014, 1016, 1018, 1020, 1024, 1026, and 1028 at FIG. 10C) corresponds tothe respective application. In some embodiments, the third userinterface (e.g., 1008-6, 1008-9) does not include a graphical objectcorresponding to the respective application. In some embodiments, thefirst and second graphical objects are complications and the third userinterface does not include a complication corresponding to therespective application. Thus, in some embodiments, when the electronicdevice transitions from the first mode to the second mode and updatesthe displayed user interface, the electronic device ceases to display acomplication in the second mode that was previously displayed in thefirst mode when displaying the third user interface. Removing contentfrom the displays enables the device to conserve battery power byavoiding energizing the pixels (e.g., turning off the pixels) that thecontent would otherwise use. Avoiding energizing pixels of the displayreduces the display brightness, which reduces power usage and improvesthe battery life of the device.

In some embodiments, the first time indicator (e.g., 1010 at FIG. 10A)includes one or more clock hands indicating time that are displayed at afirst brightness level. In some embodiments, the second time indicator(e.g., 1010 at FIG. 10C) includes one or more clock hands indicatingtime that are displayed at a second brightness level that is less thanthe first brightness level. In some embodiments, the third timeindicator includes one or more clock hands indicating time that aredisplayed at a third brightness level that is less than the secondbrightness level. Reducing the brightness of displayed clock hands onthe display reduces the display brightness, which reduces power usageand improves the battery life of the device.

In some embodiments, the first time indicator (e.g., 1010 at FIG. 10A)includes one or more clock hands indicating time that are displayed at afirst thickness level. In some embodiments, the second time indicator(e.g., inner portions of hands of 1010 at FIG. 10C are thinner) includesone or more clock hands indicating time that are displayed at a secondthickness level that is less than the first thickness level. In someembodiments, the third time indicator includes one or more handsindicating time that are displayed at a third thickness level that isless than the second thickness level. Reducing the thickness of visualelements on the display enables the device to conserve battery power byavoiding energizing the pixels that the visual elements previously used(e.g., by turning off the pixels not required to display the less-thickversion of the visual element). Avoiding energizing pixels of thedisplay reduces the display brightness, which reduces power usage andimproves the battery life of the device.

In some embodiments, the first user interface includes a first set oftick marks (e.g., indicating locations corresponding to respectivetimes) displayed with a fourth thickness. In some embodiments, thesecond user interface (e.g., 1008-3) includes a second set of tick marks(e.g., 1012 at FIG. 10C) (e.g., indicating locations corresponding torespective times) displayed with a fifth thickness that is less than thefourth thickness (e.g., without displaying the first set of tick marks).In some embodiments, the third user interface includes a third set oftick marks with a sixth thickness that is less than the fifth thickness(e.g., without displaying the first or second tick marks). Reducing thethickness of visual elements on the display enables the device toconserve battery power by avoiding energizing the pixels that the visualelements previously used (e.g., by turning off the pixels not requiredto display the less-thick version of the visual element). Avoidingenergizing pixels of the display reduces the display brightness, whichreduces power usage and improves the battery life of the device.

In some embodiments, a rate of change (e.g., illustrated by change inshading between 1008-1 and 1008-3 of elements 1010 and 1016) inbrightness for transitioning from display of the first time indicator todisplay of the second time indicator is faster than the rate of changein brightness for transitioning from display of the first graphicalobject to the second graphical object.

In some embodiments, the second user interface (e.g., 1008-3, 1008-7)includes a first complication corresponding to a first application andthe third user interface (e.g., 1008-6, 1008-9) includes a secondcomplication corresponding to the first application and a third timeindicator. In some embodiments, a difference in brightness between thesecond time indicator and the first complication is less than adifferent in brightness between the third time indicator and the secondcomplication.

In some embodiments, the first user interface (e.g., 1008-1) includes afirst graphical element (e.g., 1028 of FIG. 10A) of a second color. Insome embodiments, the second user (e.g., 1008-3) interface includes asecond graphical element (e.g., 1028 of FIG. 10C) corresponding to thefirst graphical element, wherein the second graphical element is of athird color (e.g., black, gray) different from the second color.Changing certain colored elements (e.g., white-colored, lighter colored)to a different color allows the device reduce the brightness of elementsthat more significantly affect battery consumption and to mitigate thenegative effects of displaying bright content at the same location onthe display, such as display burn-in, while at the same time reducingthe display brightness, which reduces power usage and improves thebattery life of the device.

In some embodiments, a background of the first user interface (e.g.,1008-1) has a third color that is different from a color of the firsttime indicator. In some embodiments, the second time indicator isdisplayed in the third color in the second user interface (e.g.,1008-3).

In some embodiments, the first user interface (e.g., 1008-1) includes afirst level of color saturation. In some embodiments, the second userinterface (e.g., 1008-3) includes a second level of color saturationthat is different from (e.g., less than or greater than) the first levelof color saturation. In some embodiments, the technique reduces thecolor saturation of graphical elements when transitioning from the firstmode to the second mode. In some embodiments, the technique reduces thecolor saturation to zero, thereby displaying the user interfaces inmonochrome. In some embodiments, the technique reduces the colorsaturation to zero for certain colors while not reducing the colorsaturation to zero (but optionally still reducing) for other colors.Reducing the saturation of colors (or of certain colors or elements)mitigates the negative effects of displaying content at the samelocation on the display, such as display burn-in, while at the same timereducing the display brightness, which reduces power usage and improvesthe battery life of the device.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIGS. 11A-11B) are also applicable in an analogousmanner to the methods described above/below. For example, methods 700,900, 1300, 1500, 1700, and 1900 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1100. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

FIGS. 12A-12I illustrate exemplary techniques for displaying userinterfaces, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 13. In particular, FIGS. 12A-12Iillustrate techniques for managing display usage by updating displayedcontent on a user interface at different time intervals (e.g., atdifferent rates) based in part on a current device mode (e.g., standarddisplay mode and low power display mode as described above with respectto FIG. 6A-6C).

FIGS. 12A-12D depict device 600 in standard display mode at fourdifferent times (e.g., at 10:09:01, 10:09:02, 10:10:01, and 10:10:02 aslabeled). FIGS. 12A-12D illustrate how various elements of a displayedclock face user interface update over time while device 600 operates instandard display mode (e.g., as described above).

In FIG. 12A, at a time of 10:09:01, device 600 displays clock face userinterface 1208-1. In some embodiments, clock face user interface 1208-1corresponds to or is the same as clock face user interface 608-1. Asdepicted in FIG. 12A, clock face user interface 1208-1 includes analogindication of time 1210, time scale 1212, date affordance 1214, compassaffordance 1218, timer affordance 1220, heart rate affordance 1222, andstopwatch affordance 1226 (e.g., as described above with respect tosimilar elements illustrated in FIG. 6A). Additionally, clock face userinterface 1208-1 includes cellular affordance 1278, noise affordance1280, and music affordance 1282.

Cellular affordance 1278 includes four circular indicators (e.g., dots)which change appearance in response to changes to a cellular signalstrength detected by device 600 (e.g., circular indicators appearing aseither solidly-colored or as outlines, a greater number ofsolidly-colored circular indicators representing a stronger detectedsignal strength). As depicted in FIG. 12A, cellular affordance 1278includes four solidly-colored circular dots indicating a strong cellularsignal strength. In some embodiments, the circular indicators areremoved to indicate a signal strength that has fallen below a thresholdstrength (e.g., to indicate no cellular signal or no cellularconnectivity).

Noise affordance 1280 includes graphical (e.g., meter graphic),numerical (e.g., “40 dB”), and symbolic (e.g., check mark) indicatorswhich update in response to changes to one or more environmental noiselevels detected by device 600. The graphical indicator includesradially-oriented segments which are sequentially emphasized (e.g.,transitioned from a first visual appearance to a second visualappearance) in a clockwise direction as a detected noise levelincreases, and vice versa. In some embodiments, the radially-orientedsegments are emphasized with a color based in part on a threshold noiselevel (e.g., emphasized segments are green when a detected noise levelis below a threshold noise level and yellow when a detected noise levelis not below the threshold noise level). In some embodiments, the statusindicator is updated based in part on a threshold noise level (e.g.,including an “OK” or a first graphical element (e.g., a checkmark) whenthe noise level is below a threshold and “LOUD” or a second graphicalelement (e.g., an exclamation point) when the noise level is at or abovethe threshold). In some embodiments, the graphical, numerical, andsymbolic indicators are based on different sampling windows of the samenoise data and as a result, update at different rates (e.g., graphicaland numerical indicators based on an averaged detected noise level overa 1-second window; symbolic indicator based on an averaged detectednoise level over a 1-second window). As depicted in FIG. 12A, at10:09:01, noise affordance 1280 indicates detected noise level of40-decibels (e.g., “40 dB”) which is below a threshold value (e.g., asindicated by the check mark).

Music affordance 1282 includes a graphical icon (e.g., musical note)surrounded by a circular progress indicator depicting a playbackposition associated with a music application on device 600 (e.g., aplayback position of a media file currently being played or accessed bythe music application). As a playback position advances, a portion ofthe circular progress indicator is progressively emphasized (e.g.,transitioned from a first visual appearance to a second visualappearance) in a clockwise direction, beginning at the top of theaffordance (e.g., beginning at the twelve o'clock position). As depictedin FIG. 12A, music affordance 1282 indicates a first playback position(e.g., the emphasized portion of the circular progress indicator beginsat the twelve o'clock position and ends at the three o'clock position,occupying 25% of the ring). At FIG. 12B, at a time of 10:09:02, device600 displays clock face user interface 1208-2. In FIG. 12B, device 600displays updated depictions of analog indication of time 1210, musicaffordance 1282, timer affordance 1220, and stopwatch affordance 1226indicating that 1-second has elapsed since device 600 displayed clockface user interface 1208-1. For example, the seconds hand of analogindication of time 1210 had progressed, the playback position indicatedby music affordance 1282 has increased (e.g., the emphasized portion ofthe circular progress indicator of music affordance 1282 has grownslightly beyond the 3-o'clock position depicted in FIG. 12A), timeraffordance 1220 has decremented, and stopwatch affordance hasincremented, each by an amount corresponding to 1-second. In someembodiments, updating displayed content as discussed above, includeswaking a processor of device 600 or performing processing tasksassociated with displaying content.

At FIG. 12C, at a time of 10:10:01, device 600 displays clock face userinterface 1208-3. In FIG. 12D, device 600 displays updated depictions ofanalog indication of time 1210, music affordance 1282, timer affordance1220, and stopwatch affordance 1226 indicating that 59-seconds haveelapsed since device 600 displayed clock face user interface 1208-2. Forexample, as depicted in FIG. 12C, the emphasized portion of the circularprogress indicator of music affordance 1282 has grown well beyond theposition depicted in FIG. 12B).

At FIG. 12D, at a time of 10:10:02, device 600 displays clock face userinterface 1208-4. In FIG. 12D, device 600 displays updated depictions ofanalog indication of time 1210, music affordance 1282, timer affordance1220, and stopwatch affordance 1226, indicating that 1-second haselapsed since device 600 displayed clock face user interface 1208-3. Forexample, as depicted in FIG. 12C, the emphasized portion of the circularprogress indicator of music affordance 1282 has grown slightly beyondthe position depicted in FIG. 12C).

FIGS. 12E-12H depict device 600 after transitioning to low power displaymode (e.g., as describe above with respect to FIG. 6A-6C) at the samepoints in time described above with respect to FIGS. 12A-12D (e.g., at10:09:01, 10:09:02, 10:10:01, and 10:10:02). In some embodiments, priorto transitioning from standard display mode to low power display mode,device 600 pre-computes content for display in low power display mode(e.g., device 600 determines what content will need to be displayed inlow power display mode, prepares representations (e.g., images) of thecontent, and store the prepared representations for periodic retrievaland display while in low-power display). FIGS. 12E-12H illustrate howcorresponding elements of a displayed clock face user interface updatedifferently in low power display mode than in standard display mode. Asdepicted in FIGS. 12E-12H, device 600 displays each respective clockface user interface at a lower brightness level than the correspondingclock face user interfaces displayed in FIGS. 12A-12D.

At FIG. 12E, at a time of 10:09:01, device 600 displays clock face userinterface 1208-5. In some embodiments, clock face user interface 1208-5corresponds to or is the same as clock face user interface 608-3. Asdepicted in FIG. 12E, clock face user interface 1208-5 includes analogindication of time 1210 indicating a current time of 10:09 relative totime scale 1212, date affordance 1214 indicating a current date (e.g.,“FRI 23”), timer affordance 1220 indicating 14 minutes remaining on anassociated timer, and music affordance 1282 indicating a first playbackposition (e.g., as described in FIG. 12A). Additionally, clock face userinterface 1208-5 includes stopwatch affordance 1226 and cellularaffordance 1278, which do not indicate data while device 600 operates inlow power mode. In some embodiments, stopwatch affordance 1226 displaysminutes data (e.g., does not display second-level data) while in lowpower mode similar to timer affordance 1220.

As depicted in FIG. 12E, while in low power display mode, device 600displays analog indication of time 1210, cellular affordance 1278, noiseaffordance 1280, and music affordance 1282 differently relative to theirrespective appearances in clock face user interface 1208-1 (e.g., eachaffordance is displayed at a lower brightness, and in some cases,includes less content in low power display mode than in standard displaymode). As depicted in FIG. 12E, elements associated with data thatupdates at least every second (e.g., data that updates each second ormore often than each second) have been removed (e.g., compared to clockface user interface 1208-1). For example, as depicted in FIG. 12E,analog indication of time 1210 no longer includes a seconds hands,compass affordance 1218 no longer includes directional indicators, timeraffordance 1220 no longer includes an indication of seconds, cellularaffordance 1278 no longer includes circular indicators to indicate asignal strength, and noise affordance 1280 no longer includesindications of one or more noise levels. In some embodiments, whiledevice 600 operates in low power display mode, music affordance 1282does not include an indication of a playback position.

In some embodiments, music affordance 1282 includes a track description(e.g., a song title) in place of or in addition to the circular progressindicator. While operating in standard display and low power displaymodes, device 600 updates the track description (e.g., to indicate amedia file currently being played or accessed) in a manner correspondingto the updates to performed to the progress indicator as describedherein. For example, while in standard display mode, device 600 updatesthe track description every second (e.g., at 10:09:02, 10:10:01, and10:10:02 as depicted in FIGS. 12A-12D). In contrast, while in low powerdisplay mode, device 600 updates the track description every minute(e.g., at 10:10:01 as depicted in FIGS. 12E-12H).

At FIG. 12F, at a time of 10:09:02, device 600 displays clock face userinterface 1208-6. As depicted in FIG. 12F, clock face user interface1208-6 is identical to clock face user interface 1208-5 despite thepassage of time from 10:09:01 to 10:09:02. That is, compared to device600 updating each second while in standard display as depicted in FIGS.12A-12B, while operating in low power display mode, device 600 updatesdisplayed content every minute (e.g., device 600 updates displayed dataless frequently (e.g., at a decreased rate; at increased timeintervals)).

At FIG. 12G, at a time of 10:10:01, device 600 displays clock face userinterface 1208-7. In FIG. 12G, device 600 displays updated depictions ofanalog indication of time 1210, timer affordance 1220, and musicaffordance 1282 indicating that 1-minute has elapsed since device 600displayed clock face user interface 1208-5. For example, as depicted inFIG. 12G, the emphasized portion of the circular progress indicator ofmusic affordance 1282 has grown beyond the position depicted in FIGS.12E and 12F.

At FIG. 12H, at a time of 10:10:02, device 600 displays clock face userinterface 1208-8. As depicted in FIG. 12H, clock face user interface1208-8 is identical to clock face user interface 1208-7 despite thepassage of time from 10:10:01 to 10:10:02. In some embodiments, device600 continues updating every minute while in low power display mode. Insome embodiments, rather than update every minute while in low powerdisplay mode, device 600 updates displayed content at a differentinterval of time (e.g., at 30-second intervals, at 5-minute intervals,etc.).

FIG. 12I is a chart depicting various affordances that can be includedon a clock face user interface, in accordance with some embodiments. Asdepicted in FIG. 12I, the appearance of a respective affordance candiffer based on a device mode (e.g., standard display mode or low powerdisplay mode) and application state (e.g., pause or not paused). Forexample, elements of an affordance corresponding to data that updatesfrequently (e.g., every second) while device 600 operates in standarddisplay mode, are not included in the corresponding low power moderepresentations of the same affordance.

FIG. 13 is a flow diagram illustrating a method for managing displayusage using an electronic device in accordance with some embodiments.Method 1300 is performed at a device (e.g., 100, 300, 500, 600, a smartwatch, a smart phone, a tablet computer) with a display. Some operationsin method 1300 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1300 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

The electronic device (e.g., device 600) displays (1302) a userinterface (e.g., 1208-1) that includes a plurality of user interfaceelements including a graphical representation (e.g., 1220 at FIG. 12A)of a first type of information that is associated with a firstapplication.

While (1304) the electronic device is in a first mode (e.g., a higherpower consumption mode), the electronic device (e.g., device 600)updates (1306) the appearance of the graphical representation of thefirst type of information over time with a first update interval (e.g.,transition from 1208-1 to 1208-2).

While (1304) the electronic device is in the first mode (e.g., a higherpower consumption mode) and after updating the appearance of thegraphical representation of the first type of information over time oneor more times at the first update interval, the electronic device (e.g.,device 600) detects (1308) that the electronic device has met criteriafor transitioning from the first mode to a second mode.

In response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode, the electronicdevice (e.g., device 600) transitions (1310) the electronic device fromthe first mode (e.g., a higher power consumption mode) to the secondmode (e.g., a lower power consumption mode). As discussed above ingreater detail, the first mode and the second mode are different modesin which the electronic device can operate.

While the electronic device is in the second mode, the electronic device(e.g., device 600) updates (1312) the appearance of the graphicalrepresentation of the first type of information (e.g., 1220 at FIG. 12E)over time with a second update interval (e.g., transition from 1208-5 to1208-7) that is different from the first update interval. Changing theinterval at which the appearance of graphical elements are displayedenables the device to reduce processing time (e.g., calculations) forgraphics processor(s) and general purpose processor(s), because feweruser interfaces need to be generated. The reduction in processing time,enables processors to operate in a very low power state for longerperiods of time (e.g., when user interfaces are not changing), and thusactivity at the device does not need to be monitored, which reducespower usage and improves the battery life of the device.

In some embodiments, the plurality of user interface elements includes agraphical representation (e.g., 1282 at FIG. 12A) of a second type ofinformation that is associated with a second application (e.g., datareceived from the application is optionally displayed as part of thegraphical representation). While the electronic device is in the firstmode (e.g., a higher power consumption mode), the electronic device(e.g., device 600) updates the appearance of the graphicalrepresentation (e.g., transition from 1208-1 to 1208-2) of the secondtype of information over time with a third update interval (e.g., sameas or different from the first update interval). In some embodiments,detecting that the electronic device has met criteria for transitioningfrom the first mode to the second mode occurs after updating theappearance of the graphical representation of the second type ofinformation over time one or more times at the third update interval.While the electronic device is in the second mode, the electronic device(e.g., 600) updates the appearance of the graphical representation(e.g., 1282 at FIG. 12E) of the second type of information over timewith a fourth update interval (e.g., transition from 1208-5 to 1208-7)(e.g., the same as or different from the second update interval) that isdifferent from the third update interval. Changing the interval at whichthe appearance of graphical elements are displayed enables the device toreduce processing time (e.g., calculations) for graphics processor(s)and general purpose processor(s), because fewer user interfaces need tobe generated and displayed. The reduction in processing time enablesprocessors to operate in a very low power state for longer periods oftime (e.g., when user interfaces are not changing), and thus activity atthe device does not need to be monitored, which reduces power usage andimproves the battery life of the device.

In some embodiments, displaying the user interface that includes theplurality of user interface elements includes displaying, as part of theuser interface and concurrently with the graphical representation of thefirst type of information, a time indicator (e.g., 1210) (e.g., watchhands that indicate the current time, digital readout that indicates thecurrent time, an analog clock hand (hour, minute, second hand); adigital clock numeral (hour, minute, second numerals).

In some embodiments, while the electronic device is operating in thefirst mode, the electronic device (e.g., 600) updates the time indicator(e.g., 1210 at FIGS. 12A-12B) over time with a fifth update interval.While the electronic device is operating in the second mode, theelectronic device (e.g., 600) updates updating the time indicator (e.g.,1210 at FIGS. 12E-12G) over time with a sixth update interval that isdifferent from the fifth update interval (e.g., slower than the thirdupdate interval). In some embodiments, the time indicator is updatedevery second while in the first mode and updated every minute while inthe second mode. Changing the interval at which the appearance ofgraphical elements are displayed enables the device to reduce processingtime (e.g., calculations) for graphics processor(s) and general purposeprocessor(s), because fewer user interfaces need to be generated anddisplayed. The reduction in processing time, enables processors tooperate in a very low power state for longer periods of time (e.g., whenuser interfaces are not changing), and thus activity at the device doesnot need to be monitored, which reduces power usage and improves thebattery life of the device.

In some embodiments, the graphical representation (e.g., 1220 and 1282at FIGS. 12A-12D) of the first type of information displayed in thefirst mode has one or more visual characteristics that are differentfrom the graphical representation (e.g., 1220 and 1282 at FIGS. 12E-12H)of the first type of information displayed in the second mode. In someembodiments, the graphical representation is displayed at a higherbrightness level in the first mode than in the second mode. In someembodiments, the graphical representation is displayed at a larger sizein the first mode than in the second mode. In some embodiments, thegraphical representation is displayed in color in the first mode and inmonochrome in the second mode or, more generally, has a different levelof color saturation.

In some embodiments, the first mode (e.g., operation of device 600 inFIGS. 12A-12D) is a higher power consumption mode (e.g., higher powerconsumption via the display of the electronic device and/or one or moreprocessors). In some embodiments, the second mode (e.g., operation ofdevice 600 in FIGS. 12E-12H) is a lower power consumption mode. In someembodiments, the electronic device (e.g., 600) consumes more power inthe higher power consumption mode than in the lower power consumptionmode.

In some embodiments, the first update interval is based on an activitylevel of the first application. In some embodiments, the second updateinterval is not based on the activity level of the first application. Insome embodiments, both the first update interval and the second updateinterval are based on the activity level of the first application.Changing the interval at which the appearance of graphical elements aredisplayed based on the activity level of the corresponding applicationsenables the device to conserve battery power by, for example, avoidingunnecessarily checking for information from the application that is notavailable or updating the display when new information would not beavailable, which reduces power usage and improves the battery life ofthe device. As a result, more active applications cause thecorresponding graphical elements to be updated more frequently whileless active applications cause the corresponding graphical element to beupdated less frequently.

In some embodiments, updating the appearance of the graphicalrepresentation of the first type of information includes displaying ananimation (e.g., display 1208-1 to 1208-4). In some embodiments,updating the appearance of the first type of information in the firstmode includes displaying the animation and updating the appearance ofthe first type of information in the second mode does not includedisplaying the animation.

In some embodiments, a first display brightness (e.g., Average PixelLuminance (APL)) of the display (e.g., display 602 at FIGS. 12A-12D)while the electronic device is in the first mode (e.g., a higher powerconsumption mode) is higher than a second display brightness (e.g., APL)of the display (e.g., display 602 at FIGS. 12E-12H) while the electronicdevice is in the second mode (e.g., a lower power consumption mode).Thus, the overall brightness of the display is reduced when theelectronic device transitions from the first mode to the second mode.Reducing the brightness of the display reduces power usage and improvesthe battery life of the device.

In some embodiments, while the electronic device is in the second mode,the electronic device (e.g., 600) displays an indication (e.g., removalof 1210 in FIGS. 12E-12H) (e.g., concurrently with the graphicalrepresentation of the first type of information) that the updateinterval of the graphical representation of the first type ofinformation has changed. In some embodiments, the second update intervalis longer than the first update interval and the electronic devicedisplays an indication that the rate of updates of the first type ofinformation has reduced. Displaying an indication that the updateinterval has changed provides the user with feedback about the status ofthe device and the update frequency of the first type of information.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, in response to detecting that the electronic devicehas met the criteria for transitioning from the first mode to the secondmode, the electronic device (e.g., 600) computes (e.g., prior totransitioning to the second mode) animation frames for the graphicalrepresentation of the first type of information to be displayed whilethe electronic device is in the second mode (e.g., to use to update theappearance of the graphical representation of the first type ofinformation over time with the second update interval). In someembodiments, frames for graphical representations that can be accuratelypredicted (e.g., upcoming calendar event, song progress) for display inthe second mode are computed in the first mode. Computing animationframes for display in the second mode (e.g., before entering the secondmode) enables the device to avoid computing the animation frames whilein the second mode, thereby allowing those processing components to beput to sleep, which reduces power usage and improves the battery life ofthe device. Computing animation frames for display in the second mode(e.g., before entering the second mode) enables the device to displaythe animation frames while in the low power consumption mode, therebyproviding the user with visual feedback. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the plurality of user interface elements includes agraphical representation of a third type of information that isassociated with a third application (e.g., data received from theapplication is optionally displayed as part of the graphicalrepresentation). In some embodiments, while the electronic device isoperating in the first mode, the electronic device (e.g., 600) updatesthe appearance of the graphical representation of the third type ofinformation over time with a seventh update interval. While theelectronic device is operating in the second mode, the electronic device(e.g., 600) forgoes updating (e.g., maintaining) the appearance of thegraphical representation of the third type of information over.

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described above/below. For example, methods 700, 900,1100, 1500, 1700, and 1900 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1300. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

FIGS. 14A-14E illustrate exemplary devices and user interfaces formanaging display usage, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 15.

In particular, FIGS. 14A-14E illustrate techniques for managing displayusage by altering one or more aspects (e.g., visual characteristics) ofa displayed user interface upon determining that the device has met amode-transition criteria, such as the mode-transition criteria describedin greater detail above.

FIG. 14A illustrates the same electronic device 600 at four differenttimes, as indicated by time 1410. Time 1410 is not part of the userinterface of device 600. Time 1410 is provided for the betterunderstanding of the concepts described.

At FIG. 14A at time 1410 a, device 600 displays a user interface 1402 ofa timer application while device 600 is in a standard display mode. Userinterface 1402 includes title 1402 a (“Timer”) of the timer application,current time 1402 b, a countdown timer 1402 c, cancel affordance 1402 d,and pause affordance 1402 e. Countdown timer 1402 c indicates that thereare 2 minutes and 58 seconds left on the timer, at which point device600 will provide an alert (visual, audio, and/or tactile) that the timerhas expired. Title 1402 a is displayed in a color (e.g., orange)different from the color (e.g., white) of current time 1402 b and color(e.g., white) of countdown timer 1402 c. Cancel affordance 1402 d, whenactivated (e.g., via a tap input on cancel affordance 1402 d), causesthe countdown of countdown timer 1402 c to be canceled. Pause affordance1402 e, when activated (e.g., via a tap input on pause affordance 1402e), causes the countdown of countdown timer 1402 c to be paused. Thebackground of user interface 1402 is black.

At FIG. 14A at time 1410 b, 15 seconds have elapsed since time 1410 a.Countdown timer 1402 c reflects this elapsed time, now indicating that 2minutes and 43 seconds are left on the timer. Device 600 has determinedthat the device has met the mode-transition criteria (e.g., detecting awrist-down gesture using, for example, motion sensors; no input ofcertain types for 15 seconds). In response to the determination thatdevice 600 has met the mode-transition criteria, device 600 hastransitioned to a low power display mode and replaced user interface1402 with user interface 1404. User interface 1404 is a lower powerconsumption interface of the timer application and is displayed, atleast in part, because the timer application has a lower powerconsumption interface. User interface 1404 does not include the currenttime (e.g., 1402 b) and does not include affordances (e.g., 1402 d, 1402e) for canceling or pausing the countdown of countdown timer 1402 c.Title 1402 a has changed in color (e.g., from orange) to gray, therebyreducing the amount of power consumed by the display (e.g., takes lesspower to display gray pixels than it does to display orange pixels).Countdown timer 1402 c has also changed in color, from white to gray,thereby also reducing the amount of power consumed by the display. Inthis example, the size and location of countdown timer 1402 c has notchanged between user interface 1402 and user interface 1404. Thebackground of user interface 1404 is black. In the examples of FIG. 14A,user interface 1404 is a monochrome user interface. The monochrome userinterface varies in color from black to gray (and not white). Userinterface 1404 has a lower brightness level than user interface 1402. Insome examples, user interface 1404 does include a time indicator, suchas described below with respect to FIGS. 18G-18H. In some examples, userinterface 1404 (which is specific to the timer application or which canaccommodate the information the timer application displays) isdisplayed, rather than a clock face user interface (such as 1406, whichis not specific to the timer application and which does not accommodatedisplay of the information the timer application displays) because thetimer application has a specific user interface for low power operation(e.g., a lower power consumption interface), which device 600 uses fordisplay while in the low power display mode.

At FIG. 14A at time 1410 c, 1 second has elapsed since time 1410 b.Countdown timer 1402 c reflects this elapsed time, now indicating that 2minutes and 42 seconds are left on the timer. While in the low powerdisplay mode and while displaying user interface 1404, device 600detects tap user input 1450 a on a touch-sensitive display of device600. In response to detecting tap user input 1450 a (and regardless ofthe location of the detected tap user input 1450 a on thetouch-sensitive display), device 600 transitions back to the standarddisplay mode. In response to detecting tap user input 1450 a (andregardless of the location of the detected tap user input 1450 a on thetouch-sensitive display) and because device 600 detected tap user input1450 a within a predetermined period of time (e.g., within 2 seconds) oftransitioning to displaying user interface 1404, device 600 replacesuser interface 1404 with user interface 1402, as shown in FIG. 14A attime 1410 d.

At FIG. 14A at time 1410 d, 1 second has elapsed since time 1410 c.Countdown timer 1402 c reflects this elapsed time, now indicating that 2minutes and 41 seconds are left on the timer. Device 600 is in thestandard display mode. Title 1402 a is displayed again, as well asaffordances 1402 d and 1402 e. Cancel affordance 1402 d, when activated(e.g., via a tap input on cancel affordance 1402 d), causes thecountdown of countdown timer 1402 c to be canceled. Pause affordance1402 e, when activated (e.g., via a tap input on pause affordance 1402e), causes the countdown of countdown timer 1402 c to be paused.Countdown timer 1402 c returns to being displayed in white (rather thangray). The background of user interface 1402 is black.

The timer application continues to execute throughout the times in FIG.14A, as reflected in the countdown timer 1402 c that continues to beupdated. In addition, device 600 will provide an alert once countdowntimer 1402 c expires, regardless of whether the device is in thestandard display mode or the low power display mode.

FIG. 14B illustrates the same electronic device 600 at five differenttimes, as indicated by time 1412. Time 1412 is not part of the userinterface of device 600. Time 1412 is provided for the betterunderstanding of the concepts described.

At FIG. 14B at time 1412 a, device 600 displays a user interface 1402 ofa timer application while device 600 is in a standard display mode. Userinterface 1402 is the same user interface as displayed in FIG. 14A attime 1410 a.

At FIG. 14B at time 1412 b, 15 seconds have elapsed since time 1410 a.Countdown timer 1402 c reflects this elapsed time, now indicating that 2minutes and 43 seconds are left on the timer. Device 600 has determinedthat the device has met the mode-transition criteria (e.g., detecting awrist-down gesture using, for example, motion sensors; no input ofcertain types for 15 seconds). In response to the determination thatdevice 600 has met the mode-transition criteria, device 600 hastransitioned to the low power display mode and replaced user interface1402 with user interface 1404. User interface 1404 is the same userinterface as displayed in FIG. 14A at time 1410 b. User interface 1404is a lower power consumption interface of the timer application and isdisplayed when the device transitions to the low power display modebecause the timer application has a lower power consumption interface.

At FIG. 14B at time 1412 c, 2 seconds have elapsed since time 1412 b. Inresponse to determining that the predetermined period of time (e.g., 2seconds) has elapsed since transitioning to displaying user interface1404 without detecting a tap user input (and because the timerapplication is determined to not be a particular application type (e.g.,is not identified as being an application benefiting from continuousdisplay of the application's lower power consumption user interface)),device 600 transitions to display of clock face user interface 1406.Clock face user interface 1406 is distinct from the user interfaces1402-1404 of the timer application. Clock face user interface 1406 has alower brightness level than user interface 1402. Clock face userinterface 1406 includes date 1406 a, current time 1406 b, and variouswatch complications. The watch complications include timer complication1406 c, which displays the minutes portion of countdown timer 1402 c ina gray color (without displaying the seconds portion). The watchcomplications also include a calendar complication 1406 d, exercisecomplication 1406 e, compass complication 1406 f, and a time zonecomplication 1406 g. In some embodiments, one or more (or all) ofcomplications 1406 d-1406 g do not display data from their correspondingapplication while the device is in the low power display mode anddisplaying clock face user interface 1406. For example, in FIG. 14B attime 1412 c, compass complication 1406 f does not display a cardinaldirection. The background of user interface 1406 is black. In theexamples of FIG. 14B, user interface 1406 is a monochrome userinterface. Clock face user interface 1406 is a low power consumptionclock face.

At FIG. 14B at time 1412 d, 3 seconds have elapsed since time 1412 c.The timer application is continuing to be processed by the one or moreprocessors of device 600. While in the low power display mode and whiledisplaying clock face user interface 1406, device 600 detects tap userinput 1450 b on the touch-sensitive display of device 600. In responseto detecting tap user input 1450 b (and regardless of the location ofthe detected tap user input 1450 b on the touch-sensitive display),device 600 transitions back to the standard display mode. In response todetecting tap user input 1450 b (and regardless of the location of thedetected tap user input 1450 b on the touch-sensitive display) andbecause device 600 detected tap user input 1450 b within a secondpredetermined period of time (e.g., within 5 seconds) of transitioningto displaying clock face user interface 1406, device 600 replaces userinterface 1406 with user interface 1402, as shown in FIG. 14B at time1412 e. The timer application continues to execute throughout the timesin FIG. 14B, as reflected in the countdown timer 1402 c that isdisplayed in FIG. 14B at time 1412 e.

At FIG. 14B, while in the low power display mode and while displayingclock face user interface 1406, had device 600 detected a tap user inputon the touch-sensitive display of device 600 after the secondpredetermined period of time (e.g., after 5 seconds) of transitioning todisplaying clock face user interface 1406, device 600 would transitionback to the standard display mode and would replace user interface 1406with a standard clock face user interface (e.g., 1426).

FIG. 14C illustrates the same electronic device 600 at four differenttimes, as indicated by time 1414. Time 1414 is not part of the userinterface of device 600. Time 1414 is provided for the betterunderstanding of the concepts described.

At FIG. 14C at time 1414 a, device 600 displays user interface 1408 ofan activity (e.g., workout) tracking application while device 600 is ina standard display mode. User interface 1408 includes title 1408 a(“Activity”) of the activity tracking application, current time 1408 b,and three activity rings 1408 c that indicate progress towards goals ofthree different types of activities. Title 1408 a is displayed in acolor (e.g., white) that is the same as the color (e.g., white) ofcurrent time 1408 b and different from the colors (e.g., red, green,blue) of activity rings 1408 c. The background of user interface 1408 isblack.

At FIG. 14C at time 1414 b, 15 seconds have elapsed since time 1414 a.Device 600 has determined that the device has met the mode-transitioncriteria (e.g., detecting a wrist-down gesture using, for example,motion sensors; no input of certain types for 15 seconds). In responseto the determination that device 600 has met the mode-transitioncriteria, device 600 has transitioned to the low power display mode andreplaced user interface 1408 with clock face user interface 1406. Ascompared to clock face user interface 1406 in FIG. 14B, clock face userinterface 1406 in FIG. 14C includes timer complication 1406 h. Clockface user interface 1406 is displayed because the activity trackingapplication does not have a lower power consumption interface, so thedevice instead displays clock face user interface 1406. Clock face userinterface 1406 has a lower brightness level than user interface 1408.

At FIG. 14C at time 1414 c, 1 second has elapsed since time 1414 b.While in the low power display mode and while displaying clock face userinterface 1406, device 600 detects tap user input 1450 c on atouch-sensitive display of device 600. In response to detecting tap userinput 1450 c (and regardless of the location of the detected tap userinput 1450 c on the touch-sensitive display), device 600 transitionsback to the standard display mode. In response to detecting tap userinput 1450 c (and regardless of the location of the detected tap userinput 1450 c on the touch-sensitive display) and because device 600detected tap user input 1450 c within the predetermined period of time(e.g., within 2 seconds) of transitioning to displaying clock face userinterface 1406, device 600 replaces clock face user interface 1406 withuser interface 1408, as shown in FIG. 14C at time 1414 d.

At FIG. 14C at time 1414 d, 1 second has elapsed since time 1414 c.Device 600 is in the standard display mode and is displaying userinterface 1408 of the activity tracking application as updated toreflect any additional activity tracked during the time the device wasin the low power display mode. The activity tracking applicationcontinues to execute throughout the times in FIG. 14C.

FIG. 14D illustrates the same electronic device 600 at four differenttimes, as indicated by time 1416. Time 1416 is not part of the userinterface of device 600. Time 1416 is provided for the betterunderstanding of the concepts described.

At FIG. 14D at time 1416 a, device 600 displays user interface 1408 ofthe activity (e.g., workout) tracking application while device 600 is inthe standard display mode. User interface 1408 is the same userinterface as displayed in FIG. 14C at time 1414 a.

At FIG. 14D at time 1416 b, 15 seconds have elapsed since time 1416 a.Device 600 has determined that the device has met the mode-transitioncriteria (e.g., detecting a wrist-down gesture using, for example,motion sensors; no input of certain types for 15 seconds). In responseto the determination that device 600 has met the mode-transitioncriteria, device 600 has transitioned to the low power display mode andreplaced user interface 1408 with clock face user interface 1406. Clockface user interface 1406 is the same user interface as displayed in FIG.14C at time 1414 b. Clock face user interface 1406 displayed because theactivity tracking application does not have a lower power consumptioninterface, so device 600 instead displays clock face user interface1406. Clock face user interface 1406 is a lower power consumption userinterface and has a lower brightness level than user interface 1408.

At FIG. 14D at time 1416 c, 3 seconds have elapsed since time 1416 b.While in the low power display mode and while displaying clock face userinterface 1406, device 600 detects tap user input 1450 d on thetouch-sensitive display of device 600. In response to detecting tap userinput 1450 d (and regardless of the location of the detected tap userinput 1450 d on the touch-sensitive display), device 600 transitionsback to the standard display mode. In response to detecting tap userinput 1450 d (and regardless of the location of the detected tap userinput 1450 d on the touch-sensitive display) and because device 600detected tap user input 1450 d after the predetermined period of time(e.g., outside of 2 seconds) of transitioning to displaying clock faceuser interface 1406, device 600 replaces clock face user interface 1406with standard clock face user interface 1426, as shown in FIG. 14D attime 1416 d.

At FIG. 14D at time 1416 d, 1 second has elapsed since time 1416 c.Device 600 is in the standard display mode and is displaying standardclock face user interface 1426. The standard clock face user interface1426 has a higher brightness level than clock face user interface 1406.Date 1426 a is larger than and brighter than date 1406 a. Current time1426 b is larger than and brighter than current time 1406 b. Similarly,complications 1426 c-1426 g are larger than and brighter than thecorresponding complications 1406 c-1406 g of clock face user interface1406. Complications 1406 c-1406 g of standard clock face user interface1426 update more frequently than the corresponding complications ofclock face user interface 1406, as described in greater detail withrespect to method 1300, FIG. 13, and the corresponding description.Compass complication 1426 f displays a cardinal direction based on thedetected orientation of electronic device 600 (as compared to compasscomplication 1416 f, which does not display the cardinal direction).

FIG. 14E illustrates the same electronic device 600 at four differenttimes, as indicated by time 1418. Time 1418 is not part of the userinterface of device 600. Time 1418 is provided for the betterunderstanding of the concepts described.

At FIG. 14E at time 1418 a, device 600 displays user interface 1420 of aworkout application while device 600 is in a standard display mode. Userinterface 1420 includes title 1420 a (“Workout”) of the workoutapplication, current time 1420 b, elapsed workout time indicator 1420 c,calories indicator 1420 d, distance indicator 1420 e, and applicationicon 1420 f, all of which are displayed using a white color. Device 600is displaying an indication (e.g., in response to receiving user inputto select elapsed workout time indicator 1420 c) that elapsed workouttime indicator 1420 c is selected by displaying elapsed workout timeindicator in bold (e.g., as compared to 1420 d-1420 e, which are not inbold). The background of user interface 1420 is black.

At FIG. 14E at time 1418 b, 15 seconds have elapsed since time 1418 a.Device 600 has determined that the device has met the mode-transitioncriteria (e.g., detecting a wrist-down gesture using, for example,motion sensors; no input of certain types for 5, 10 or 15 seconds). Inresponse to the determination that device 600 has met themode-transition criteria, device 600 has transitioned to a low powerdisplay mode and replaced user interface 1420 with user interface 1422.User interface 1422 is a lower power consumption interface of theworkout application and is displayed because the workout application hasa lower power consumption interface. User interface 1422 includes title1420 a (“Workout”) of the workout application, current time 1420 b,abbreviated elapsed workout time indicator 1420 g, calories indicator1420 d, distance indicator 1420 e, and application icon 1420 f, all ofwhich are displayed using a gray color (which consumes less energy todisplay than a white color). Abbreviated elapsed workout time indicator1420 g displays hours and seconds of elapsed time without displayinghundredths of seconds of elapsed time. In contrast, elapsed workout timeindicator 1420 c displays a higher precision value of elapsed time bydisplaying hours, seconds, and hundredths of seconds of elapsed time.Reducing the precision of the displayed elapsed time while displayinguser interface 1422 enables the device to reduce the quantity of pixelsused to display the time, thereby reducing power consumption of thedisplay of the time, and to reduce the processing power required tocalculate and/or display the higher precision time, thereby furtherreducing power consumption of the display of the time. Device 600updates calories indicator 1420 d and distance indicator 1420 e lessfrequently (at longer intervals) than at which abbreviated elapsedworkout time indicator 1420 g is displayed because abbreviated elapsedworkout time indicator 1420 g is selected (as was indicated by thebolding of 1420 c). Device 600 displays calories indicator 1420 d anddistance indicator 1420 e at a lower brightness level than at whichabbreviated elapsed workout time indicator 1420 g is displayed becauseabbreviated elapsed workout time indicator 1420 g is selected (as wasindicated by the bolding of 1420 c). Device 600 also updates caloriesindicator 1420 d and distance indicator 1420 e less frequently (atlonger intervals) than were previously updated while the device was inthe standard display mode and was displaying user interface 1420. In theexamples of FIG. 14A, user interface 1422 is a monochrome userinterface. The monochrome user interface varies in color from black togray (and not white). User interface 1422 has a lower brightness levelthan user interface 1420.

At FIG. 14E at time 1418 c, 1 minute has elapsed since time 1418 b.Abbreviated elapsed workout time indicator 1420 g reflects this elapsedtime, now indicating that 1 minute and 16 seconds have elapsed. Incontrast to the technique in FIG. 14B, device 600 has not transitioneddevice 600 to display clock face user interface 1406 despite thepredetermined period of time (e.g., 2 seconds) having elapsed sincetransitioning to displaying user interface 1422 without detecting a tapuser input. Device 600 has not transitioned device 600 to display clockface user interface 1406 and has instead maintained display of userinterface 1422 because the workout application is determined to be aparticular application type (e.g., identified as benefiting fromcontinuous display of the application's lower power consumption userinterface). Because device 600 has determined the workout application tobe of the particular application type, device 600 forgoes replacing userinterface 1422 with display clock face user interface 1406.

At FIG. 14E at time 1418 c, while in the low power display mode andwhile displaying user interface 1422, device 600 detects tap user input1450 e on a touch-sensitive display of device 600. In response todetecting tap user input 1450 e (and regardless of the location of thedetected tap user input 1450 e on the touch-sensitive display), device600 transitions back to the standard display mode. In response todetecting tap user input 1450 e (and regardless of the location of thedetected tap user input 1450 c on the touch-sensitive display) andbecause device 600 detected tap user input 1450 e (regardless of whethertap user input 1450 e is detected before or after the predeterminedperiod of time (e.g., within 2 seconds) of transitioning to displayinguser interface 1422), device 600 replaces user interface 1422 with userinterface 1420, as shown in FIG. 14E at time 1418 d.

At FIG. 14E at time 1418 d, 1 second has elapsed since time 1418 c.Elapsed workout time indicator 1420 c reflects this elapsed time, nowindicating that 1 minute, 17 seconds, and 18 hundredths of seconds haveelapsed. Device 600 is in the standard display mode. While in thestandard display mode and displaying user interface 1420, device 600updates the display updates calories indicator 1420 d and distanceindicator 1420 e with the same frequency with which elapsed workout timeindicator 1420 c is displayed. Device 600 updates calories indicator1420 d and distance indicator 1420 e more frequently (at shorterintervals) than were previously updated while in the low power displaymode and displaying user interface 1422. The workout applicationcontinues to execute throughout the times in FIG. 14E, as reflected inthe elapsed workout time indicator 1420 c that continues to be updated.

FIG. 15 is a flow diagram illustrating a method for managing displayusage using an electronic device in accordance with some embodiments.Method 1500 is performed at a device (e.g., 100, 300, 500, 600) with adisplay. Some operations in method 1500 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1500 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

While the electronic device (e.g., 600) is operating in a first mode(e.g., a higher power consumption mode), the electronic device (e.g.,600) displays (1502), on the display, a first user interface (e.g., ahigher power consumption interface; 1402 of FIG. 14A at 1410 a, 1402 atFIG. 14B at 1412 a, 1408 at FIG. 14C at 1414 a, 1408 at FIG. 14D at 1416a, 1420 at FIG. 14E at 1418 a) of a first application (e.g., aninstalled application distinct from the operating system; an interfacecorresponding to an application operating in the foreground). The firstuser interface includes a first graphical object (e.g., 1402 c, 1420 c)corresponding to (e.g., generated by) the first application (e.g., agraphical object that includes information provided by the firstapplication).

While displaying the first user interface, the electronic device (e.g.,600) detects (1504) that the electronic device (e.g., 600) has metcriteria for transitioning from the first mode to a second mode (e.g., alower power consumption mode).

In some embodiments, in response (1506) to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode (e.g., criteria that are indicative of reduced userinteraction with the electronic device (e.g., timeout expiration,accelerometer data indicating wrist down, touch data indicating palmover gesture)), the electronic device (e.g., 600) transitions theelectronic device from the first mode to the second mode in response todetecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode. As discussed abovein greater detail, the first mode and the second mode are differentmodes in which the electronic device can operate.

In response (1506) to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode and inaccordance with a determination that the first application is anapplication of a first type (e.g., an application that includes a lowerpower consumption interface), the electronic device (e.g., 600) replaces(1508) display of the first user interface (e.g., 1402, 1420) of thefirst application with a second user interface (e.g., a lower powerconsumption interface, 1404 of FIG. 14A at 1410 b, 1404 of FIG. 14B at1412 b, 1422 of FIG. 14E at 1418 b) of the first application differentfrom the first user interface (e.g., lower power interface differs fromthe higher power interface in one or more visual characteristics (sizeof elements, color, hue, saturation, opacity, shape)), the second userinterface including a second graphical object (e.g., 1402 c, 1420 g)corresponding to the first application (e.g., a graphical object thatincludes information provided by the first application). In someembodiments, the second graphical object is the first graphical object.In some embodiments, the second graphical object corresponds to thefirst graphical object (e.g., the second graphical object includes thesame information as the first graphical object).

In response (1506) to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode and inaccordance with a determination that the first application is anapplication of a second type (e.g., an application that does not includea lower power consumption interface), the electronic device (e.g., 600)replaces (1510) display of the first user interface (e.g., 1408 of FIG.14C at 1414 a, 1408 at FIG. 14D at 1416 a,) of the first applicationwith a third user interface (e.g., a clock face of a smart watch, 1406of FIG. 14C at 1414 b, 1406 at FIG. 14D at 1416 b) different from thefirst user interface of the first application and the second userinterface of the first application. The third user interface that is anoperating system user interface including one or more elements (e.g.,1406 d, 1406 e, 1406 f) that are not part of the first user interface ofthe first application (In some embodiments, and not part of the seconduser interface of the first application), including a time indicator(e.g., an analog clock hand (hour, minute, second hand); a digital clocknumeral (hour, minute, second numerals; 1406 i). In some embodiments,the third user interface is not generated by the first application. Insome embodiments, the third user interface does not include graphicalobjects (e.g., any graphical objects) generated by the first application(e.g., does not include graphical objects that include informationprovided by the first application).

Displaying a lower power consumption interface of an application whenavailable enables the device to continue to show information specific tothat application while in the lower power consumption mode, yet stillallows the device to achieve the lower power consumption mode when thelower power consumption interface is not available for the applicationby displaying a lower power consumption watch face. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, while the electronic device (e.g., 600) is in thesecond mode and is displaying the third user interface (e.g., 1406 ofFIG. 14C at 1414 b), the electronic device (e.g., 600) detects that theelectronic device has met a first set of criteria for transitioning fromthe second mode to the first mode. In some embodiments, the first set ofcriteria for transitioning from the second mode to the first mode aremet with the electronic device detects a user input (e.g., detecting awrist raise gesture, detecting a touch gesture, such as a tap, on atouch-sensitive surface of the electronic device). In response todetecting that the electronic device has met the first set of criteriafor transitioning from the second mode to the first mode, the electronicdevice (e.g., 600) replaces display of the third user interface (e.g.,1406 of FIG. 14C at 1414 b-1414 c) with display of the first userinterface (e.g., 1408 of FIG. 14C at 1414 d) including the firstgraphical object generated (e.g., 1408 c) by the first application.

In some embodiments, while the electronic device (e.g., 600) is in thesecond mode and is displaying the third user interface (e.g., 1406 ofFIG. 14C at 1414 b, 1406 at FIG. 14D at 1416 b), the electronic device(e.g., 600) detects that the electronic device has met a second set ofcriteria for transitioning from the second mode to the first mode. Insome embodiments, the second set of criteria for transitioning from thesecond mode to the first mode are met with the electronic device detectsa user input (e.g., detecting a wrist raise gesture, detecting a touchgesture, such as a tap, on a touch-sensitive surface of the electronicdevice). In response to detecting that the electronic device has met thesecond set of criteria for transitioning from the second mode to thefirst mode, the electronic device (e.g., 600) replaces (e.g., inaccordance with a determination that the first user interface was not asystem user interface, in accordance with a determination that the userinput was not received within a threshold period of time, such as 2seconds) display of the third user interface (e.g., a first clock faceof a smart watch; 1406 of FIG. 14C at 1414 d) with display of a fourthuser interface (e.g., 1426 of FIG. 14D at 1416 d) different from thefirst user interface of the first application, the second user interfaceof the first application, and the third user interface, wherein thefourth user interface is an operating system user interface includingone or more elements (e.g., 1426 d-1426 g) that are not part of the userinterface of the first application, including a second time indicator(e.g., 1426 b) that is different in one or more characteristics (e.g.,bigger, brighter, different color) from the time indicator of the thirduser interface. In some embodiments, the second time indicator isdisplayed at a brightness level that is higher than a brightness levelof the time indicator of the third user interface. In some embodiments,the second time indicator is smaller in size than the time indicator ofthe third user interface. In some embodiments, the second time indicatoris a different color than the time indicator of the third userinterface.

Displaying a brighter user interface when the device detects that theuser is attempting to interact with the device provides the user withfeedback that the device has left the lower power consumption mode.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the second set of criteria for transitioning fromthe second mode to the first mode includes a criterion that is met whenthe electronic device (e.g., 600) detects a wrist raise gesture (e.g.,detected using one or more motion sensors of the electronic device todetect the device changing in orientation to an orientation that isfacing upward at an angle). Displaying a brighter user interface whenthe device detects that the user is performing a wrist raise gesture tointeract with the device provides the user with feedback that the devicehas left the lower power consumption mode. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the second set of criteria for transitioning fromthe second mode to the first mode includes a criterion that is met whenthe electronic device detects a tap gesture (e.g., 1450 d, detectedusing a touch-sensitive surface of the electronic device).

Displaying a brighter user interface when the device detects that theuser is performing a tap gesture to interact with the device providesthe user with feedback that the device has left the lower powerconsumption mode. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves thebattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, while the electronic device is in the second modeand is displaying the second user interface, the electronic device(e.g., 600) detects that the electronic device has met a third set ofcriteria for transitioning from the second mode to the first mode. Insome embodiments, the third set of criteria for transitioning from thesecond mode to the first mode are met with the electronic device detectsa user input (e.g., detecting a wrist raise gesture, detecting a touchgesture, such as a tap, on a touch-sensitive surface of the electronicdevice) (within the threshold period of time). In response to detectingthat the electronic device has met the third set of criteria fortransitioning from the second mode to the first mode, the electronicdevice (e.g., 600) replaces (e.g., in accordance with a determinationthat the first user interface was not a system user interface, inaccordance with a determination that the user input was received withinthe threshold period of time, such as 2 seconds) display of the seconduser interface with display of the first user interface (e.g., 1402 ofFIG. 14A at 1410 d, an updated version of the first user interface(e.g., based on updated information from the first application)including the first graphical object (e.g., 1402 c) corresponding to(e.g., generated by) the first application.

Displaying a brighter user interface when the device detects that theuser is attempting to interact with the device provides the user withfeedback that the device has left the lower power consumption mode.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, while the electronic device is in the second modeand is displaying the third user interface (e.g., 1406 of FIG. 14C at1414 b, 1406 at FIG. 14D at 1416 b), the electronic device (e.g., 600)detects that the electronic device has met a fourth set of criteria fortransitioning from the second mode to the first mode that includes acriterion that is met when the electronic device detects a user input(e.g., detecting a wrist raise gesture, detecting a touch gesture, suchas a tap, on a touch-sensitive surface of the electronic device).

In some embodiments, in response to detecting that the electronic devicehas met the fourth set of criteria for transitioning from the secondmode to the first mode: in accordance with a determination that a set ofcriteria is met (e.g., the set of criteria including one or more of: atime-from-input criterion that is met when the user input is detectedwithin a threshold period of time (e.g., 2 seconds, 5 seconds) of theelectronic device transitioning to the second mode, a touch-gesturecriterion that is met when the user input is a touch gesture detected ona touch-sensitive surface of the electronic device, a tap-gesturecriterion that is met when the user input is a tap gesture detected onthe touch-sensitive surface of the electronic device, and awrist-raise-gesture that is met when the user input is a wrist-raisegesture detected using one or more sensors (e.g., motion sensors) of theelectronic device), the electronic device (e.g., 600) replaces displayof the third user interface with display of the first user interface(e.g., 1402 at FIG. 14B at 1412 e) including the first graphical object(e.g., 1402 c) corresponding to (e.g., generated by) the firstapplication, wherein the set of criteria includes a criterion that ismet when the user input is detected within a threshold period of time ofthe electronic device transitioning to the second mode.

In some embodiments, in response to detecting that the electronic devicehas met the fourth set of criteria for transitioning from the secondmode to the first mode: in accordance with a determination that the setof criteria is not met (e.g., input is detected after the thresholdperiod of time, after 5 seconds), replacing display of the third userinterface (e.g., 1406 at FIG. 14D at 1416 c, a first clock face of asmart watch) with display of a fifth user interface (e.g., 1426 at FIG.14D at 1416 d, a brighter clock face of a smart watch) different fromthe first user interface of the first application, the second userinterface of the first application, and the third user interface,wherein the fifth user interface is an operating system user interfaceincluding one or more elements (e.g., 1426 d-1426 g) that are not partof the user interface of the first application, including a third timeindicator (e.g., 1426 b) that is different in one or morecharacteristics from the time indicator (e.g., 1406 i) of the third userinterface. In some embodiments, the third time indicator is displayed ata brightness level that is higher than a brightness level of the timeindicator of the third user interface. In some embodiments, the secondtime indicator is smaller in size than the time indicator of the thirduser interface. In some embodiments, the second time indicator is adifferent color than the time indicator of the third user interface.

In some embodiments, the user input is a wrist raise gesture (e.g.,detected using one or more motion sensors of the electronic device). Insome embodiments, the input type criterion is satisfied if the userinput is a wrist raise gesture. Displaying a brighter user interfacewhen the device detects that the user is performing a wrist raisegesture to interact with the device provides the user with feedback thatthe device has left the lower power consumption mode. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the user input is a tap gesture (e.g., 1450 c, 1450d, detected using a touch-sensitive surface of the electronic device).In some embodiments, the input type criterion is satisfied if the userinput is a tap gesture. In some embodiments, the input type criterion issatisfied if the user input is either a tap gesture or a wrist raisegesture. In some embodiments, the threshold period of time varies basedon the type of input received. In some examples, the threshold period oftime is shorter when the user input is a tap input and longer when theuser input is a wrist raise gesture. Displaying a brighter userinterface when the device detects that the user is performing a tapgesture to interact with the device provides the user with feedback thatthe device has left the lower power consumption mode. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the first graphical object (e.g., 1402 c, 1420 c)(or a another graphical object, such as 1402 d, 1402 e) is displayedwith a first visual characteristic (e.g., in a first color) in the firstuser interface and the first graphical object (or the another graphicalobject 1402 d, 1402 e), when selected in the first user interface,activates a first function (e.g., device detecting tap gesture on thefirst graphical object causes a corresponding function (e.g., a functionrelated to the first application) to be performed). For example, cancelwhen affordance 1402 d is pressed, pause when affordance 1402 e ispressed.

In some embodiments, the first graphical object (or the anothergraphical object 1402 d, 1402 e) is displayed with a second visualcharacteristic (e.g., in a second color, such as in a darker coloraffordance in 1404 of FIG. 14A) in the second user interface differentfrom the first visual characteristic and the first graphical object,when selected in the second user interface, does not cause activation ofthe first function (e.g., does not cause activation of any function;causes activation of a function other than the first function (e.g.,causes a transition from the second mode to the first mode)). In someembodiments, the appearance of the first graphical object changes toindicate whether the graphical object is activatable. Displaying anindication that certain graphical objects cannot be activated in certainmodes provides the user with feedback about what inputs will and willnot perform functions and reduces unnecessary user inputs. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the first graphical object (e.g., 1420 c) (e.g., afirst metric provided by a workout application) is a selected graphicalobject (e.g., is visually distinguished (e.g., by highlighting, bybolding, by being different in size) from other graphical objects of thefirst user interface (e.g., indicating that it is selected and/orhighlighted for further action)). In some embodiments, only onegraphical object can be selected at a time and selection of anothergraphical object deselects the first graphical object. In someembodiments, the first application is a workout application (e.g., aphysical activity tracking application. In some embodiments, the firstuser interface of the first application includes a third graphicalobject (e.g., 1420 d-1420 e in FIG. 14E at 1418 a, a second metricprovided by a workout application) corresponding to the firstapplication that is not a selected graphical object.

In some embodiments, replacing display of the first user interface ofthe first application with a second user interface (e.g., a lower powerconsumption interface) of the first application different from the firstuser interface includes: in accordance with a determination that thesecond graphical object (e.g., 1420 g) corresponds to the selected firstgraphical object (e.g., the second graphical object includes at least aportion of the same information as the first graphical object), theelectronic device (e.g., 600) displays the second graphical object(e.g., 1420 g) at a first brightness level (e.g., average pixelluminance (APL), average lumen output, total lumen output, averageilluminance, or total illuminance of the indicator on the display;brightness expressed in nits, lux, or lumens); and in accordance with adetermination that the second graphical object (e.g., 1420 d-1420 e inFIG. 14E at 1418 b) corresponds to the third graphical object that isnot a selected object (e.g., does not correspond to the selected firstgraphical object), the electronic device (e.g., 600) displays the secondgraphical object at a second brightness level that is less than thefirst brightness level. In some embodiments, the first application is aworkout application that tracks workout information/metric (e.g., steps,distance, heartrate) of a user and the first graphical object and thesecond graphical object display the same workout metric. In someembodiments, while in the second mode, the second user interface for thefirst application displays a selected graphical object at a brightnesslevel that is brighter than the brightness level of graphical objectsthat are not selected. Differentiating between selected and unselectedgraphical elements for brightness control enables the device to showselected elements (e.g., that is particularly relevant to the user) atan appropriate brightness level so that the user can more readily accessthe selected information, yet reduce the overall display brightness,which reduces power usage and improves the battery life of the device.

In some embodiments, after displaying the second graphical object (e.g.,1420 g at 1418 b) at the first brightness level, the electronic device(e.g., 600) displays, on the display, a second instance of the firstuser interface with the first graphical object as a selected object. theelectronic device (e.g., 600) detects a set of one or more inputscorresponding to a request to select the third graphical object. Inresponse to detecting the set of one or more inputs corresponding to arequest to select the third graphical object: the electronic device(e.g., 600) selects the third graphical object and de-selecting thefirst graphical object. In some embodiments, displaying the thirdgraphical object with one or more visual characteristics that indicatethat it is selected (e.g., by highlighting, by bolding, by beingdifferent in size) from other graphical objects of the first userinterface (e.g., indicating that it is selected and/or highlighted forfurther action)). While the third graphical object is selected, theelectronic device (e.g., 600) detects that the electronic device has metcriteria for transitioning from the first mode to a second mode. Inresponse to detecting that the electronic device has met criteria fortransitioning from the first mode to a second mode while the thirdgraphical object is detected, the electronic device (e.g., 600) replacesdisplay of the second instance of the first user interface with a secondinstance of the second user interface that includes a fourth graphicalobject that: in accordance with a determination that the fourthgraphical object corresponds to the first graphical object that is notselected, is displayed at a third brightness level; and in accordancewith a determination that the fourth graphical object corresponds to thethird graphical object that is selected, is displayed at a fourthbrightness level that is greater than the third brightness level. Insome embodiments, selecting a different graphical object (e.g., while inthe first user interface) causes a graphical object of the second userinterface that corresponds to the newly selected graphical object to bedisplayed with a brightness level that is greater than the brightness ofa graphical object of the second user interface that corresponds to thepreviously selected (but no longer selected) graphical object of thefirst user interface. Differentiating between selected and unselectedgraphical elements for brightness control enables the device to showselected elements (e.g., that is particularly relevant to the user) atan appropriate brightness level so that the user can more readily accessthe selected information, yet reduce the overall display brightness,which reduces power usage and improves the battery life of the device.

In some embodiments, the fourth graphical object updates with a shorterupdate interval than the second graphical object based on the thirdgraphical object having been selected. In some embodiments, graphicalobjects in the second user interface that correspond to selectedgraphical object in the first user interface update with shorter updateintervals than graphical objects in the second user interface that donot correspond to selected graphical objects in the first userinterface. Differentiating between selected and unselected graphicalelements for frequency of updates enables the device to update selectedelements (e.g., that is particularly relevant to the user) atappropriate intervals so that the user can more readily access theselected information, yet reduce the overall processing required for theuser interface, which reduces power usage and improves the battery lifeof the device.

In some embodiments, the electronic device (e.g., 600) displays, on thedisplay, a fourth user interface (e.g., a higher power consumptioninterface) of (e.g., generated by) a second application (e.g., aninstalled application distinct from the operating system; an interfacecorresponding to an application operating in the foreground) that isdifferent from the first application, the fourth user interfaceincluding a fifth graphical object corresponding to (e.g., generated by)the second application (e.g., a graphical object that includesinformation provided by the second application). While displaying thefourth user interface, the electronic device (e.g., 600) detects thatthe electronic device has met the criteria for transitioning from thefirst mode to the second mode. In response to detecting that theelectronic device has met the criteria for transitioning from the firstmode to the second mode (e.g., criteria that are indicative of reduceduser interaction with the electronic device (e.g., timeout expiration,accelerometer data indicating wrist down, touch data indicating palmover gesture)): in accordance with a determination that the secondapplication is an application of the first type (e.g., an applicationthat includes a lower power consumption interface), the electronicdevice (e.g., 600) replaces display of the fourth user interface of thesecond application with a fifth user interface (e.g., a lower powerconsumption interface) of the second application different from thefourth user interface (e.g., lower power interface differs from thehigher power interface in one or more visual characteristics (size ofelements, color, hue, saturation, opacity, shape)), the fifth userinterface including a sixth graphical object corresponding to the secondapplication (e.g., a graphical object that includes information providedby the second application). In some embodiments, the sixth graphicalobject is the fifth graphical object. In some embodiments, the sixthgraphical object corresponds to the fifth graphical object (e.g., thesixth graphical object includes the same information as the fifthgraphical object). In some embodiments, in accordance with adetermination that the second application is an application of thesecond type (e.g., an application that does not include a lower powerconsumption interface), the electronic device (e.g., 600) replacesdisplay of the fourth user interface of the second application with thethird user interface (e.g., a clock face of a smart watch). In someembodiments, the third user interface is not generated by the secondapplication. In some embodiments, the third user interface is differentfrom the fifth user interface of the second application and the sixthuser interface of the second application. In some embodiments, the thirduser interface does not include graphical objects (e.g., any graphicalobjects) generated by the second application (e.g., does not includegraphical objects that include information provided by the secondapplication).

In some embodiments, display of the first user interface (e.g., 1402 ofFIG. 14A at 1410 a, 1402 at FIG. 14B at 1412 a, 1408 at FIG. 14C at 1414a, 1408 at FIG. 14D at 1416 a, 1420 at FIG. 14E at 1418 a) is at abrightness level above a threshold brightness level, display of thesecond user interface (e.g., 1404 of FIG. 14A at 1410 b, 1404 of FIG.14B at 1412 b, 1422 of FIG. 14E at 1418 b) is at a brightness levelbelow the threshold brightness level, and display of the third userinterface (e.g., 1406 of FIG. 14C at 1414 b, 1406 at FIG. 14D at 1416 b)is at a brightness level (e.g., same as or different from the brightnesslevel of the second user interface) below the threshold brightnesslevel. Reducing the brightness of the display below the thresholdbrightness level when in the lower power consumption mode reduces powerusage and improves the battery life of the device.

In some embodiments, in response to detecting that the electronic device(e.g., 600) has met criteria for transitioning from the first mode tothe second mode, prior to replacing display of the first user interface(e.g., 1408 at FIG. 14D at 1416 a) of the first application with thethird user interface (e.g., 1406 at FIG. 14D at 1416 b), the electronicdevice (e.g., 600) reduces a brightness of the first user interface. Insome embodiments, the electronic device slightly dims the first userinterface before replacing the first user interface with the third userinterface.

In some embodiments, the third user interface includes a graphicalobject (e.g., 1406 f associated with a compass application) associatedwith a third application (e.g., the graphical object is a complicationthat displays information received from the third application) and agraphical object associated (e.g., 1406 g associated with a world timeapplication) with a fourth application (e.g., the graphical object is acomplication that displays information received from the fourthapplication).

In some embodiments, while the electronic device is operating in thefirst mode, the electronic device (e.g., 600) displays, on the display,a system user interface (e.g., 1818 of FIG. 18I) generated by theoperating system (e.g., a plurality of icons that when activated causedisplay of a corresponding application user interface, a plurality oficons that when activated toggle a system setting (such as wifi on/off,bluetooth on/off)). While displaying the system user interface (e.g.,1818 of FIG. 18I) generated by the operating system, the electronicdevice (e.g., 600) detects that the electronic device has met a sixthset of criteria for transitioning from the first mode to the secondmode. In some embodiments, the sixth set of criteria for transitioningfrom the first mode to the second mode are met when the electronicdevice detects that the user has moved their wrist that is wearing theelectronic device from a raised position to a non-raised position, suchas detecting a wrist down gesture. In some embodiments, the sixth set ofcriteria for transitioning from the first mode to the second mode aremet when the electronic device detects a tap input on the touch-screendisplay of the device. In response to detecting that the electronicdevice has met the fifth set of criteria for transitioning from thefirst mode to the second mode: the electronic device (e.g., 600)transitions from the first mode to the second mode.

In some embodiments, in response to detecting that the electronic devicehas met the fifth set of criteria for transitioning from the first modeto the second mode: in accordance with the electronic device displayingthe system user interface when the sixth set of criteria fortransitioning from the first mode to the second mode are met, replacingdisplay of the system user interface (e.g., 1818 of FIG. 18I) generatedby the operating system with a clock face user interface (e.g., 1822 ofFIG. 18K, 1824 of FIG. 18L; a clock face of a smart watch) differentfrom the system user interface, the clock face user interface being anoperating system user interface including one or more elements that arenot part of the system user interface, including a time indicator (e.g.,an analog clock hand (hour, minute, second hand); a digital clocknumeral (hour, minute, second numerals). In some embodiments, the clockface user interface does not include graphical objects (e.g., anygraphical objects) from the system user interface.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIG. 15) are also applicable in an analogous mannerto the methods described above/below. For example, methods 700, 900,1100, 1300, 1700, and 1900 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1500. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

FIGS. 16A-16F illustrate exemplary devices and user interfaces formanaging display usage, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 17A-17B.

In particular, FIGS. 16A-16F illustrate techniques for managing displayusage by altering one or more aspects (e.g., visual characteristics) ofa displayed user interface upon determining that the device has met amode-transition criteria, such as the mode-transition criteria describedin greater detail above.

FIGS. 16A-16B illustrate a transition from a higher power consumptionuser interface to a lower power consumption user interface (using afirst template) while displaying a stopwatch application.

FIG. 16A illustrates electronic device 600 displaying user interface1602 of a stopwatch application while device 600 is in the standarddisplay mode. User interface 1602 is a higher power consumption userinterface. User interface 1602 includes title 1602 a (“Digital”) of thestopwatch application (indicating it is displaying a digital stopwatch),current time 1602 b, a stopwatch timer 1602 c, lap affordance 1602 d,and stop affordance 1602 e. Stopwatch timer 1602 c indicates that 3seconds and 29 hundredths of seconds have elapsed since the stopwatchtimer was started. Title 1602 a is displayed in a color (e.g., white)that is the same as the color (e.g., white) of current time 1602 b andcolor (e.g., white) of stopwatch timer 1602 c. Lap affordance 1602 d,when activated (e.g., via a tap input on lap affordance 1602 d), causesthe stopwatch application to display a lap time. Stop affordance 1602 e,when activated (e.g., via a tap input on pause affordance 1602 e),causes stopwatch timer 1602 c to stop running. The background of userinterface 1602 is black. The stopwatch application determines thearrangement of the graphical elements of user interface 1602. Thestopwatch application also determines the sizing, color, and content ofthe graphical elements of user interface 1602.

While displaying user interface 1602 of the stopwatch application,device 600 determines that the device has met the mode-transitioncriteria (e.g., detecting a wrist-down gesture using, for example,motion sensors; no input of certain types for 15 seconds). In responseto the determination that device 600 has met the mode-transitioncriteria, device 600 transitions to a low power display mode andreplaces user interface 1602 with user interface 1604. User interface1604 is a lower power consumption interface (as compared to 1602) and isdisplayed using the first template (e.g., based on device 600 havingdetermined that the timer application corresponds to the firsttemplate).

FIG. 16B illustrates electronic device 600 displaying user interface1604 while device 600 is in the low power display mode. User interface1604 relies on the first template to include title 1604 a (“Digital”) ofthe stopwatch application (indicating digital stopwatch) and stopwatchtimer 1604 c. The first template optionally specifies one or more of:the quantity of graphical elements, the color of graphical elements(e.g., gray), the size of graphical elements (larger size for the timer,smaller size for the title), the location of graphical elements (e.g.,centered on display for the timer), the brightness level of graphicalelements, the background color (e.g., black), the font of text, and theprecision with which data is displayed. User interface 1604 does notinclude current time (e.g., 1602 b), a lap affordance (e.g., 1602 d), ora stop affordance (e.g., 1602 e) because, for example, the firsttemplate only accommodates a single type of information (e.g., a time)to be displayed in addition to the title. In the examples of FIGS.6A-6B, stopwatch timer 1604 c is displayed at a larger size thanstopwatch timer 1602 c. Title 1604 a and stopwatch timer 1604 c aredisplayed in a gray color. The background of user interface 1604 isblack. User interface 1604 has a lower brightness level than userinterface 1602.

In some embodiments, the stopwatch application provides the time forstopwatch timer 1604 c, but the stopwatch application is not able tospecify (e.g., because the operating system of device 600 specifies) thecolor, size, location, font, and/or precision with which to display thetimer, for device 600 to display user interface 1604 in the low powerdisplay mode.

FIGS. 16C-16D illustrate a transition from a higher power consumptionuser interface to a lower power consumption user interface (using thefirst template) while displaying a music application.

FIG. 16C illustrates electronic device 600 displaying user interface1606 of a music application while device 600 is in the standard displaymode. User interface 1606 is a higher power consumption user interface.User interface 1606 includes title 1606 a (“Music”) of the musicapplication, current time 1606 b, song name 1606 c (“Track 1”), artistname 1606 d (“DJ Appleseed”), playback controls 1606 e (which, whenactivated, skip to the beginning of the current song, pause the currentsong, and skip to a next song), and controls 1606 f (which, whenactivated, enable changing settings of the music application). Title1606 a, time 1606 b, song name 1606 c, artist name 1606 d, playbackcontrols 1606 e, and controls 1606 f are optionally displayed in thesame color (e.g., white) in user interface 1606. The background of userinterface 1606 is black. The music application determines thearrangement of the graphical elements (e.g., 1606 c, 1606 d, 1606 e) ofuser interface 1606. The music application also determines the sizing,color, and content of the graphical elements of user interface 1606.

While displaying user interface 1606 of the music application, device600 determines that device 600 has met the mode-transition criteria(e.g., detecting a wrist-down gesture using, for example, motionsensors; no input of certain types for 15 seconds). In response to thedetermination that device 600 has met the mode-transition criteria,device 600 transitions to a low power display mode and replaces userinterface 1606 with user interface 1608. User interface 1608 is a lowerpower consumption interface (as compared to 1606) and is displayed usingthe first template (e.g., based on device 600 having determined that themusic application corresponds to the first template).

FIG. 16D illustrates electronic device 600 displaying user interface1608 while device 600 is in the low power display mode. User interface1608 relies on the first template to include title 1608 a (“Music”) ofthe music application and song name 1608 c. The first templateoptionally specifies one or more of: the quantity of graphical elements,the color of graphical elements (e.g., gray), the size of graphicalelements (larger size for the song name, smaller size for the title),the location of graphical elements (e.g., song name centered ondisplay), the brightness level of graphical elements, the backgroundcolor (e.g., black), the font of text, and the precision with which datais displayed. User interface 1608 does not include current time (e.g.,1606 b), artist name (e.g., 1606 d), playback controls (e.g., 1606 e),or controls (e.g., 1606 f) because, for example, the first template onlyaccommodates a single type of information (e.g., a song name) to bedisplayed in addition to the title. In the examples of FIGS. 6C-6D, songname 1608 c is displayed at a larger size than song name 1606 c. Title1608 a and song name 1608 c are displayed in a gray color. Thebackground of user interface 1608 is black. User interface 1608 has alower brightness level than user interface 1606.

In some embodiments, the music application provides the name for songname 1608 c, but the music application is not able to specify the color,size, location, font, and/or precision with which to display the name,for device 600 to display user interface 1608 in the low power displaymode.

Because user interface 1604 and 1608 both use the same first template,they have various visual characteristics in common. In some embodiments,the location, size, color, and font of title 1604 a is the same as thoseof 1608 a. In some embodiments, the location, size, color, and font ofstopwatch timer 1604 c is the same as those of song name 1608 c. In someembodiments, the background color of user interface 1604 and 1608 is thesame color. In some embodiments, user interface 1604 and 1608 eachinclude only two fields (e.g., for title and for stopwatch timer/songname).

FIGS. 16E-16F illustrate a transition from a higher power consumptionuser interface to a lower power consumption user interface (using asecond template) while displaying a progress tracking application.

FIG. 16E illustrates electronic device 600 displaying user interface1610 of a progress tracking application while device 600 is in thestandard display mode. User interface 1610 is a higher power consumptionuser interface. User interface 1610 includes title 1610 a (“Progress”)of the progress tracking application, current time 1610 b, time progresstext 1610 c, time progress bar 1610 d, step progress text 1610 e, andstep progress bar 1610 f. Title 1610 a, time 1610 b, time progress text1610 c, and step progress text 1610 e are optionally displayed in thesame color (e.g., white) in user interface 1610. The background of userinterface 1610 is black. The progress tracking application determinesthe arrangement of the graphical elements (e.g., 1610 c, 1610 d, 1610 e,1610 f) of user interface 1610. The progress tracking application alsodetermines the sizing, color, and content of the graphical elements ofuser interface 1610.

While displaying user interface 1610 of the progress trackingapplication, device 600 determines that device 600 has met themode-transition criteria (e.g., detecting a wrist-down gesture using,for example, motion sensors; no input of certain types for 15 seconds).In response to the determination that device 600 has met themode-transition criteria, device 600 transitions to a low power displaymode and replaces user interface 1610 with user interface 1612. Userinterface 1612 is a lower power consumption interface (as compared to1610) and is displayed using the second template (e.g., based on device600 having determined that the progress tracking application correspondsto the second template) that is different from the first template.

FIG. 16F illustrates electronic device 600 displaying user interface1612 while device 600 is in the low power display mode. User interface1612 relies on the second template to include title 1612 a of theprogress tracking application, measurement units 1612 b, and timeprogress information 1612 c. The second template optionally specifiesone or more of: the quantity of graphical elements, the color ofgraphical elements (e.g., gray), the size of graphical elements (largersize for the timer, smaller size for the title), the location ofgraphical elements (e.g., centered on display for the timer), thebrightness level of graphical elements, the background color (e.g.,black), the font of text, and the precision with which data isdisplayed. User interface 1608 does not include current time (e.g., 1610b), time progress bar (e.g., 1610 d), step progress text (e.g., 1610 e),and step progress bar (e.g., 1610 f) because, for example, the secondtemplate only accommodates a measurement unit and a set of progressinformation to be displayed in addition to the title. In the examples ofFIGS. 6E-6F, the progress of minutes is displayed in a different format,as illustrated by time progress information 1612 c. Measurement units1612 b is displayed at a smaller font as compared to time progressinformation 1612 c. Title 1612 a, measurement units 1612 b, and timeprogress information 1612 c are displayed in a gray color. Thebackground of user interface 1612 is black. User interface 1612 has alower brightness level than user interface 1610.

In some embodiments, the progress tracking application provides theunits for measurement units 1612 b and provides the progress and goalfor time progress information 1612 c, but the progress trackingapplication is not able to specify the color, size, location, font,and/or precision with which to display the information, for device 600to display user interface 1612 in the low power display mode.

Because user interface 1612 uses a second template that is differentfrom the first template used for user interface 1604 and 1608, useinterface 1612 has various visual characteristics that differ from thoseof user interfaces 1604 and 1608. In some embodiments, the location,size, color, and font of measurement units 1612 b and time progressinformation 1612 c are different from graphical elements of userinterfaces 1604 and 1608. In some embodiments, the background color ofuser interface 1604, 1608, and 1612 is the same color. In someembodiments, user interface 1604 and 1608 each include only two fields(e.g., for title and for stopwatch timer/song name), while userinterface 1612 includes more than two fields.

FIGS. 17A-17B are a flow diagram illustrating a method for managingdisplay usage using an electronic device in accordance with someembodiments. Method 1700 is performed at a device (e.g., 100, 300, 500,device 600, a smart watch, a smart phone, a tablet computer) with adisplay. Some operations in method 1700 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1700 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

While (1702) the electronic device (e.g., 600) is operating in a firstmode (e.g., a higher power consumption mode), the electronic device(e.g., 600) displays (1704), on the display, a first user interface(e.g., 1602; a higher power consumption interface) of a firstapplication with an arrangement of user interface elements (e.g., 1602c-1602 e) determined by the first application, and displays (1706), onthe display, a second user interface (e.g., 1606; a higher powerconsumption interface) of a second application with an arrangement ofuser interface elements (e.g., 1606 c-1606 f) determined by the secondapplication.

While the electronic device (e.g., 600) is operating in the first mode,the electronic device (e.g., 600) detects (1710) that the electronicdevice has met criteria for transitioning from the first mode to asecond mode (e.g., a lower power consumption mode).

In response to detecting that the electronic device has met the criteriafor transitioning from the first mode to the second mode (e.g., criteriathat are indicative of reduced user interaction with the electronicdevice (e.g., timeout expiration, accelerometer data indicating wristdown, touch data indicating palm over gesture)), the electronic device(e.g., 600) transitions (1712) from the first mode to the second mode.

Transitioning (1712) from the first mode to the second mode includes: inaccordance with a determination that the first application (e.g., 1602)was displayed on the display when the electronic device detected thatthe electronic device has met criteria for transitioning from the firstmode to a second mode, displaying (1714) information (e.g., 1604 c) fromthe first application in a predefined template (e.g., template shownused in 1604 and 1608; a preset format (e.g., comprising preset elements(e.g., graphical elements, watch complications, text elements, and/ortime indicator elements), preset sizes for elements, preset colorschemes for elements, preset brightness level schemes for elements,and/or present positions for elements); a preset arrangement; a presetlayout).

Transitioning (1712) from the first mode to the second mode includes: inaccordance with a determination that the second application (e.g., 1606)was displayed on the display when the electronic device detected thatthe electronic device has met criteria for transitioning from the firstmode to a second mode, displaying (1716) information (e.g., 1608 c) fromthe second application in the predefined template (e.g., template shownused in 1604 and 1608). As discussed above in greater detail, the firstmode and the second mode are different modes in which the electronicdevice can operate.

Displaying information from various applications using the same templateenables the device to display information from those variousapplications using a lower power consumption interface, which reducespower usage and improves the battery life of the device. Displayinginformation in the same template also provides the user with feedbackabout the state of the device (e.g., that it is in the second mode).Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, while (1702) the electronic device is operating inthe first mode (e.g., a higher power consumption mode), the electronicdevice (e.g., 600) displays (1708) a third user interface (e.g., 1610; ahigher power consumption interface) of a third application with anarrangement of user interface elements (e.g., 1610 c-1610 f) determinedby the third application. In some embodiments, transitioning (1712) fromthe first mode to the second mode includes: in accordance with adetermination that the third application (e.g., 1610) was displayed onthe display when the electronic device detected that the electronicdevice has met criteria for transitioning from the first mode to asecond mode, displaying (1718) information (e.g., 1612 b-1612 c) fromthe third application in a second predefined template (e.g., template asshown in 1612) that is different (e.g., having a different predefinedset or arrangement of elements; having the same elements but arranged ina different predefined spatial pattern) from the predefined template(e.g., template as shown in 1604 and 1608). In some embodiments,different applications use different predefined temples for displayinginformation while the electronic device is in the second mode. In someembodiments, the first application and the second application are afirst type of application and accordingly use the predefined templateand the third application is a second type of application (differentfrom the first type) and thus the second predefined template is used. Insome embodiments, the predefined template and the second predefinedtemplate include placement of user interface elements at differentpositions.

Displaying information from particular types of applications usingtemplates that correspond to the application enables the device todisplay information from those different types of applications informats appropriate for the applications in lower power consumptioninterface formats, which reduces power usage and improves the batterylife of the device.

In some embodiments, the predefined template (e.g., template as shown in1604 and 1608) is a user interface template configured for use in a lowpower consumption mode. In some embodiments, the power required todisplay the first user interface is higher than that required to displayinformation (e.g., of the first and/or the second applications) in thepredefined template. In some embodiments, displaying information of thefirst application in the predefined template requires approximately thesame amount of power as displaying the information of the secondapplication in the predefined template.

In some embodiments, the predefined template includes an icon templatefield for display of an application icon corresponding to theapplication that was displayed on the display when the electronic devicedetected that the electronic device has met criteria for transitioningfrom the first mode to a second mode.

In some embodiments, the predefined template includes an informationtemplate field (e.g., template field for displaying 1604 c, 1608 c) fordisplay of the information from the application that was displayed onthe display when the electronic device detected that the electronicdevice has met criteria for transitioning from the first mode to asecond mode.

In some embodiments, the predefined template also includes a titletemplate field for display of the name of the application or a titleprovided by the application. In some embodiments, the icon templatefield is positioned at the top of the user interface, the title templatefield is positioned below the icon template field, and the informationtemplate field is displayed below the title template field. Displayingan application icon and information from an application provides theuser with feedback about which application is providing the information.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, the first application is of a first category ofapplications (e.g., applications that require more frequent displayupdates in the second mode) and the second application is of a secondcategory of applications (e.g., applications that require less frequentupdates in the second mode) different from the first category ofinformation. While the electronic device is operating in the secondmode, the electronic device (e.g., 600) updates the information (e.g.,1604 c, 1608 c) from the application that was displayed on the displaywhen the electronic device detected that the electronic device has metcriteria for transitioning from the first mode to a second mode, overtime with an update interval that is determined based on the category ofthe application. In some embodiments, when information from the firstapplication is being displayed, the information is updated with a firstupdate interval (e.g., updated every second) and when information fromthe second application is being displayed, the information is updatedwith a second update interval (e.g., updated every two seconds) that isdifferent from the first update interval. For example, information froman application that is categorized as a workout (e.g., user exercisetracking) application is updated more frequently than information froman application that is not categorized as a workout application.

Changing the interval at which displayed information from applicationsare updated based on the category of the application enables the deviceto conserve battery power by reducing the frequency with which theinformation to be displayed is calculated and the frequency with whichthe display should be refreshed when, for example, the application is alower priority application and/or the application does not providefrequent/constant updated information, which reduces power usage andimproves the battery life of the device.

In some embodiments, the information from the first application is of afirst category of information (e.g., timer information 1604 c,information that requires more frequent display updates in the secondmode) and the information from the second application is of a secondcategory of information (e.g., track name information 1608 c,information that require less frequent updates in the second mode)different from the first category of information. While the electronicdevice is operating in the second mode, the electronic device (e.g.,600) updates display of information (e.g., 1604 c, 1608 c) from theapplication that was displayed on the display over time with an updateinterval that is determined based on the category of the information. Insome embodiments, displayed information from the first category ofinformation is updated with a first information update interval (e.g.,updated every second) and displayed information from the second categoryof information is updated with a second information update interval(e.g., updated every two seconds, ten seconds, or minute) that isdifferent from the first information update interval. For example,information that is categorized as workout (e.g., user exercisetracking) information is updated more frequently than information thatis not categorized as workout information. Changing the interval atwhich displayed information from applications are updated based on thecategory of the information enables the device to conserve battery powerby reducing the frequency with which the information to be displayed iscalculated and the frequency with which the display should be refreshedwhen, for example, the type of information is lower priority informationand/or the type of information is not time-sensitive, which reducespower usage and improves the battery life of the device.

In some embodiments, displaying the first user interface (e.g., a higherpower consumption interface) of the first application with anarrangement of user interface elements determined by the firstapplication includes displaying information of a first category ofinformation (e.g., timer information; workout information, steps taken,heart rate). In some embodiments, displaying information from the firstapplication in the predefined template includes displaying informationof the first category of information. In some embodiments, the displayedinformation from the first application in the predefined template beingvisually different (e.g., not having a hundredths of seconds field asshown in 1604 c) from the displayed information in the first userinterface by one or more visual characteristics other than color. Insome embodiments, the information displayed in the first user interfaceis a first size and the same category of information displayed using thepredefined template is in a second size different from the first size(e.g., smaller than the first size). In some embodiments, theinformation displayed in the first user interface is displayed at afirst brightness level and the same category of information displayedusing the predefined template is in at a second brightness leveldifferent from the first brightness level (e.g., less bright than thefirst brightness level).

Displaying the information from the application in visually distinctways provides the user with feedback about the state of the device.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves the battery life of the device by enabling theuser to use the device more quickly and efficiently.

In some embodiments, displaying the first user interface (e.g., 1602; ahigher power consumption interface) of the first application with anarrangement of user interface elements determined by the firstapplication includes displaying a first set of information (e.g.,minutes and seconds of 1602 c) and a second set of information (e.g.,hundredths of seconds of 1602 c). In some embodiments, displayinginformation from the first application in the predefined templateincludes displaying the first set of information (e.g., minutes andseconds of 1602 c) without displaying the second set of information(e.g., hundredths of seconds of 1602 c). In some embodiments, the amountof information displayed while in the second mode is less than theamount of information displayed while in the first mode.

In some embodiments, a first display brightness level (e.g., averagepixel luminance (APL), average lumen output, total lumen output, averageilluminance, or total illuminance of the indicator on the display;brightness expressed in nits, lux, or lumens) of the display whiledisplaying the first user interface (e.g., 1602) while the electronicdevice is in the first mode (e.g., a higher power consumption mode) ishigher than a second display brightness level of the display whiledisplaying information from the first application in the predefinedtemplate (e.g., 1604) while the electronic device is in the second mode(e.g., a lower power consumption mode). In some embodiments, a thirddisplay brightness level (e.g., Average Pixel Luminance (APL)) of thedisplay while displaying the second user interface while the electronicdevice is in the first mode (e.g., a higher power consumption mode) ishigher than a fourth display brightness level (e.g., APL, same as seconddisplay brightness) of the display while displaying information from thesecond application in the predefined template while the electronicdevice is in the second mode (e.g., a lower power consumption mode).Thus, the overall brightness of the display is reduced when displayinginformation while the electronic device is in the second mode ascompared to displaying information while the electronic device is in thefirst mode. Reducing the overall brightness of the display reduces powerusage and improves the battery life of the device, while still enablingthe user to access the device.

Note that details of the processes described above with respect tomethod 1700 (e.g., FIGS. 17A-17B) are also applicable in an analogousmanner to the methods described above/below. For example, methods 700,900, 1100, 1300, 1500, and 1900 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1700. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

FIGS. 18A-18L illustrate exemplary devices and user interfaces formanaging display usage, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 19.

In particular, FIGS. 18A-18F illustrate techniques for managing displayusage by altering one or more aspects (e.g., visual characteristics) ofa displayed user interface upon determining that the device has met amode-transition criteria, such as the mode-transition criteria describedin greater detail above.

FIGS. 18A-18F illustrate a transition from a higher power consumptionuser interface (e.g., FIG. 18A) to a lower power consumption userinterface (e.g., FIG. 18D) and back to the higher power consumption userinterface (e.g., 18F) for a user interface of a music application.

FIG. 18A illustrates electronic device 600 in the standard display modeand displaying user interface 1802 for a music application at a standarddisplay mode brightness level. User interface 1802 includes title 1802 a(e.g., “Music”) and graphical elements 1802 (e.g., a stack of albums).User interface 1802 is a higher power consumption user interfacedisplayed while device 600 is in the standard display mode. Whiledisplaying user interface 1802, device 600 determines that device 600has met the mode-transition criteria (e.g., detecting a wrist-downgesture using, for example, motion sensors; receiving no input ofcertain types for 15 seconds). In response to the determination thatdevice 600 has met the mode-transition criteria, device 600 begins totransition to a low power display mode, resulting in replacing userinterface 1802 with user interface 1804, a lower power consumption userinterface. At FIG. 18A, device 600 also displays notification indicator1840, which indicates that one or more unread notifications areavailable.

As part of the transition from user interface 1802 to user interface1804, device 600 ceases to display (e.g., fades out, blurs out) currenttime 1802 b and changes the brightness of user interface 1802 (e.g.,including title 1802 a and graphical elements 1802 c) such that they areless bright, as shown in user interface 1804 of FIG. 18B. For example,device 600 changes some (or all) white elements, such as title 1802, toa gray color, thereby reducing the amount of power the elements consumeand reducing the risk of burn-in on the display. Concurrently withreducing the brightness of user interface 1802, device 600 reduces thesize of user interface 1802, while optionally maintaining a center ofuser interface 1802, as shown in user interface 1804 of FIG. 18B.Further, device 600 applies a first level of blur to elements of userinterface 1802, as shown in user interface 1804 of FIG. 18B. As aresult, device 600 provides an animation of user interface 1802 movingbackwards in z-space and blurring out while the display reduces inbrightness. While transitioning from the interface of FIG. 18A to thatof FIG. 18B, device 600 maintains the size, location, color, and overalllook of notification indicator 1840 (e.g., no blurring). As noted bybrightness scale 630, the overall brightness of the display of device600 is higher while displaying user interface 1802 than while displayinguser interface 1804.

The transition continues, with device 600 animating changes from userinterface 1804 to user interface 1806. Device 600 displays (e.g., fadesin, blurs in) current time 1806 b and changes the brightness of userinterface 1804 (e.g., including title 1802 a and graphical elements 1802c) such that user interface 1806 is less bright as compared to userinterface 1804 and 1802, as shown in FIG. 18C. For example, device 600changes some (or all) gray elements, such as title 1802 a, to a darkergray color, thereby reducing the amount of power the elements consumeand reducing the risk of burn-in on the display. Concurrently withreducing the brightness of user interface 1804, device 600 furtherreduces the size of user interface 1804 while optionally maintaining acenter of user interface 1804, as shown in user interface 1806 of FIG.18C. Further, device 600 applies a second (additional) level of blur toelements of user interface 1804, as shown in user interface 1806 of FIG.18C. As a result, device 600 provides a further animation of userinterface 1804 moving further backwards in z-space and blurring out morewhile the display further reduces in brightness. While transitioningfrom the interface of FIG. 18B to that of FIG. 18C, device 600 continuesto maintain the size, location, color, and overall look of notificationindicator 1840 (e.g., no blurring). As noted by brightness scale 630,the overall brightness of the display of device 600 is higher whiledisplaying user interface 1804 than while displaying user interface1806. Thus, the device consumes less power while displaying userinterface 1806.

Current time 1806 b at FIG. 18C is displayed in white and is larger thancurrent time 1802 b at FIG. 18A. The location of current time 1806 b isdifferent as compared to that of current time 1802 b. For example,current time 1806 b is further from the edge of the display as comparedto current time 1802 b. For another example, current time 1806 b iscloser to the center of the display as compared to current time 1802 b.

At FIGS. 18C-18D, device 600 is in the low power display mode and isdisplaying aspects of user interfaces 1802 at a reduced size andbrightness, which include blurred out elements of the music application(e.g., 1802 a, 1802 c), and current time 1806 b, which are not blurredout. As time elapses, current time 1806 b is updated, as illustrated inthe transition between FIGS. 18C and 18D. In some embodiments, thelocation, size, and/or color of current time 1806 b changes (e.g.,changes as time progresses) between user interface 1806 and userinterface 1808 in FIGS. 18C and 18D, thereby reducing the likelihood ofburn-in of the display. In some embodiments, the blurred out contents ofthe user interface of the music application remain static (e.g., thecontents do not update, even as the music application executes) whilethe device is in the low power display mode.

While displaying user interface 1808 at FIG. 18D and while device 600 isin the low power display mode, device 600 receives a request (e.g.,detects a wrist raise gesture, detects a tap on the display of device600) to transition to the standard display mode. In response toreceiving the request to transition to the standard display mode, device600 animates a transition between user interface 1808 of FIG. 18D touser interface 1812 of FIG. 18F.

As part of the animated transition to display user interface 1812,device 600 ceases to display (e.g., fades out, blurs out) current time1806 b, as illustrated in user interface 1810 of FIG. 18E. At FIG. 18E,the overall brightness of the display has increased as compared to thedisplay of device 600 at FIG. 18D. Title 1802 a and graphical elements1802 c become larger, brighter, and less blurred as compared to userinterface 1808. Dark gray elements become less dark (e.g., light gray).While transitioning from the interface of FIG. 18D to that of FIG. 18E,device 600 maintains the size, location, color, and overall look ofnotification indicator 1840 (e.g., no blurring). As the animationcontinues, at FIG. 18F, device 600 displays (e.g., fades in, blurs in)current time 1802 b (e.g., at the same location as previously displayedcurrent time 1802 b in user interface 1802). At FIG. 18F, the overallbrightness of the display has increased as compared to the display ofdevice 600 at FIG. 18E. In user interface 1812, title 1802 a andgraphical elements 1802 c become larger, brighter, and are no longerblurred. In some examples, user interface 1812 returns to not beingmonochrome (having various colors).

FIGS. 18G-18H illustrate a transition from a higher power consumptionuser interface (e.g., FIG. 18G) to a lower power consumption userinterface (e.g., FIG. 18H) for a user interface of a timer application.In some embodiments, the timer application is the same as that describedwith reference to FIGS. 14A and 14B. For example, user interface 1814corresponds to user interface 1402.

FIG. 18G illustrates electronic device 600 in the standard display modeand displaying user interface 1814 for a timer application. Userinterface 1814 includes title 1814 a (“Timer”) of the timer application,current time 1814 b, a countdown timer 1814 c, cancel affordance 1814 d,and pause affordance 1814 e. Countdown timer 1814 c indicates that thereare 4 minutes and 58 seconds left in the timer, at which point device600 will provide an alert (visual, audio, and/or tactile) that the timerhas expired. Title 1814 a is displayed in a color (e.g., orange)different from the color (e.g., white) of current time 1814 b and color(e.g., white) of countdown timer 1814 c. Cancel affordance 1814 d, whenactivated (e.g., via a tap input on cancel affordance 1814 d), causesthe countdown of countdown timer 1814 c to be canceled. Pause affordance1814 e, when activated (e.g., via a tap input on pause affordance 1814e), causes the countdown of countdown timer 1814 c to be paused. Thebackground of user interface 1814 is black.

User interface 1814 is a higher power consumption user interfacedisplayed while device 600 is in the standard display mode. Whiledisplaying user interface 1814, device 600 determines that device 600has met the mode-transition criteria (e.g., detecting a wrist-downgesture using, for example, motion sensors; no input of certain typesfor 15 seconds). In response to the determination that device 600 hasmet the mode-transition criteria, device 600 begins to transition to alow power display mode, resulting in replacing user interface 1814 withuser interface 1816, a lower power consumption user interface.

As part of the transition from user interface 1814 to user interface1816, device 600 ceases to display (e.g., fades out, blurs out) currenttime 1802 b instead displays current time 1814 f at a larger size and ata different location. Device 600 reduces the brightness of the displaywhen transitioning from user interface 1814 to 1816. Device 600 reducesthe brightness at which title 1814 a, countdown timer 1814 c, cancelaffordance 1814 d, and pause affordance 1814 e are displayed. Forexample, device 600 changes some (or all) white elements, such as title1802, to a gray color, thereby reducing the amount of power the elementsconsume and reducing the risk of burn-in on the display. Concurrentlywith reducing the brightness of the user interface, device 600 reducesthe size of the user interface elements, while optionally maintaining acenter of the user interface, as shown in the transition between userinterface 1814 and 1816. Device 600 blurs elements of the userinterface, as shown in user interface 1816 of FIG. 18H. As a result,device 600 provides an animation of the user interface of the timerapplication moving backwards in z-space, becoming monochrome in color,and blurring out while the display reduces in brightness. As noted bybrightness scale 630, the overall brightness of the display of device600 is higher while displaying user interface 1814 as compared todisplaying user interface 1816. Thus, device 600 consumes less powerwhile in the low power display mode and is displaying user interface1816 as compared to user interface 1814. In some embodiments, whiledisplaying user interface 1814, displayed graphical elements of timerapplication optionally remain static (e.g., timer 1814 c does notupdate) while the current time 1814 f does update. As illustrated inFIG. 18H, in some embodiments, while displaying user interface 1814,some (or all) displayed graphical elements of timer application update(e.g., with various update intervals, as described above). For example,countdown timer 1814 c has been updated to reflect that one second haselapsed and thus countdown timer 1814 c indicates 4 minutes and 57seconds remaining. While device 600 is in the low power display mode, aprocess of the timer application continues to execute. For example,device 600 will alert the user once the timer of the timer applicationexpires.

FIGS. 181 and 18J illustrate device 600 operating in a standard displaymode while displaying system user interface 1818. System user interface1818 corresponds to (or is the same as) user interface 608-11, asdescribed above. In FIG. 18I, device 600 is displaying system settingsuser interface 1818, which provides the user with an easy way to:enable/disable wifi (e.g., by the device detecting a tap gesture on wifiaffordance 1818 a), check battery percentage 1818 b, turn on Do NotDisturb (e.g., by device 600 detecting a tap gesture on affordance 1818c), locating an external device (e.g., by the device detecting a tapgesture on ping affordance 1818 d), silence device 600 (e.g., by device600 detecting a tap gesture on silence affordance 1818 e), turn ontheater mode (e.g., by device 600 detecting a tap gesture on theateraffordance 1818 f).

In FIG. 18J, device 600 is displaying system notifications userinterface 1820, which provides the user with a listing of receivednotifications 1820 a-1820 b. Notification 1820 a is a receivednotification that corresponds to a workout application. When activated(e.g., detecting tap on notification 1820 a), device 600 displays theworkout application. Notification 1820 b is a received notification thatcorresponds to a payment application. When activated (e.g., detectingtap on notification 1820 b), device 600 displays the paymentapplication.

While displaying a system user interface (e.g., 1818, 1820), device 600determines that device 600 has met the mode-transition criteria (e.g.,detecting a wrist-down gesture using, for example, motion sensors; noinput of certain types for 15 seconds). In response to the determinationthat device 600 has met the mode-transition criteria, device 600 beginsto transition to a low power display mode and replaces the system userinterface (e.g., 1818, 1820) with user interface 1822, a clock face userinterface that is a lower power consumption user interface. Thus, inaccordance with a determination that the currently displayed userinterface is a system interface, device 600 replaces the systeminterface with user interface 1822, which is a lower power userinterface. As noted by brightness scale 630, the overall brightness ofthe display of device 600 is higher while displaying the system userinterface (e.g., 1818, 1820) than while displaying user interface 1822.Thus, device 600 consumes less power while displaying user interface1822. In some embodiments, in accordance with the determination that thecurrently displayed user interface is a system interface, device 600does not reduce down in size and blur out the displayed user interface(e.g., 1818, 1820) when the mode-transition criteria is met (and doeswhen the user interface is not a system interface, described above withrespect to 18A-18C and 18G-18H).

While displaying user interface 1822 at FIG. 18K and while device 600 isin the low power display mode, device 600 receives a request (e.g.,detects a wrist raise gesture, detects a tap on the display of device600) to transition to the standard display mode. In response toreceiving the request to transition to the standard display mode, device600 transitions to the standard display mode and, in accordance with adetermination that device 600 entered the low power display mode whiledevice 600 was displaying a user interface that is a system interface,device 600 displays user interface 1824 as shown in FIG. 18L, which is astandard clock face user interface (rather than returning to display ofthe system interface). Displaying standard clock user interface 1824 ishelpful for the user because the user is unlikely to want to return toaccessing a system interface (e.g., 1818, 1820) and, in the unlikelyscenario that the user does want to re-access the system interface(e.g., 1818, 1820), device 600 provides easy mechanisms (e.g., a singleswipe up gesture, a single swipe down gesture) to re-display the systeminterface (e.g., 1818, 1820). The transition between displaying userinterface 1822 (which corresponds to or is the same as user interface808-4) and 1824 (which corresponds to or is the same as 808-8) isdescribed in greater detail above with respect to the transition betweenuser interface 808-4 of FIG. 8D to user interface 808-8 in FIG. 8H.

FIG. 19 is a flow diagram illustrating a method for managing displayusage using an electronic device in accordance with some embodiments.Method 1900 is performed at a device (e.g., 100, 300, 500, 600; a smartwatch, a smart phone, a tablet computer) with a display. Some operationsin method 1900 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1900 provides an intuitive way for managingdisplay usage. The method reduces power usage and the likelihood ofscreen burn-in. The method also reduces the cognitive burden on a userfor managing display usage, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a device to automatically manage display usage faster and moreefficiently conserves power and increases the time between batterycharges.

While the electronic device (e.g., 600) is operating in a first mode,the electronic device (e.g., 600) displays (1902), on the display, afirst user interface (e.g., 1802, 1814) of (e.g., a higher powerconsumption interface) an application. The electronic device (e.g., 600)detects (1904) (e.g., while displaying the first user interface) thatthe electronic device has met criteria for transitioning from the firstmode to a second mode.

In response (1906) to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode (e.g.,criteria that are indicative of reduced user interaction with theelectronic device (e.g., timeout expiration, accelerometer dataindicating wrist down, touch data indicating palm over gesture)), theelectronic device (e.g., 600) transitions (1908) from the first mode tothe second mode. As discussed above in greater detail, the first modeand the second mode are different modes in which the electronic devicecan operate.

In response (1906) to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode (e.g.,criteria that are indicative of reduced user interaction with theelectronic device (e.g., timeout expiration, accelerometer dataindicating wrist down, touch data indicating palm over gesture)), theelectronic device (e.g., 600) replaces (1910), on the display, the firstuser interface with a second user interface (e.g., 1806, 1808, 1816; alower power consumption interface) including an obscured representation(e.g., 1802 a, 802 c, 1814 a, 1814 c, 1814 d) of at least a portion ofthe first user interface (e.g., 1802, 1814) of the application (e.g., arepresentation of the same graphical object including the same data withreduced sharpness (detail) or contrast (e.g., blurred); a representationresulting from applying a non-linear filter to the representation).

In response (1906) to detecting that the electronic device has met thecriteria for transitioning from the first mode to the second mode (e.g.,criteria that are indicative of reduced user interaction with theelectronic device (e.g., timeout expiration, accelerometer dataindicating wrist down, touch data indicating palm over gesture)), theelectronic device (e.g., 600) displays (1914) a time indicator (e.g.,1806 b, 1814 f) at a position on the display overlapping at least aportion of the obscured representation (e.g., 1802 c, 1814 c) of the atleast a portion of the first user interface (e.g., 1802, 1814) of theapplication (e.g., time overlay).

Displaying an obscured representation of the interface of theapplication provides the user with visual feedback that the device isoperating in a lower power consumption mode while still providing theuser with feedback about the application that was displayed when thedevice entered the lower power consumption mode. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the obscured representation (e.g., 1802 a, 802 c,1814 a, 1814 c, 1814 d) of at least a portion of the first userinterface (e.g., 1802, 1814) of the application is a blurred (1912)representation of at least the portion of the first user interface(e.g., 1802, 1814). In some embodiments, obscuring the representation ofthe portion of the first user interface for display includes blurringthe representation of the portion of the first user interface. Obscuringthe representation of the interface of the application provides the userwith visual feedback that the device is operating in a lower powerconsumption mode while still providing the user with feedback about theapplication that was displayed when the device entered the lower powerconsumption mode. Further, obscuring the representation of the interfaceof the application provides the user with additional security, as otherusers are less able to view the contents of the application. Providingimproved visual feedback to the user and improving security enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the first user interface (e.g., 1802,1814) of the application while in the first mode includes displaying theportion of the first user interface (e.g., 1802 c, 1814 c) of theapplication at a first size. In some embodiments, replacing the firstuser interface with the second user interface including the obscuredrepresentation of at least the portion of the first user interface ofthe application includes displaying an obscured representation of theportion of the first user interface of the application at a second sizethat is smaller than the first size (e.g., as shown in FIGS. 18C, 18D,and 18H). Reducing the display size of representation of the interfaceof the application provides the user with visual feedback that thedevice is operating in a lower power consumption mode while stillproviding the user with feedback about the application that wasdisplayed when the device entered the lower power consumption mode.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the first user interface (e.g., 1802,1814) of the application while in the first mode includes displaying theportion of the first user interface (e.g., 1802, 1814) of theapplication at a first brightness level. In some embodiments, replacingthe first user interface (e.g., 1802, 1814) with the second userinterface (e.g., 1806, 1816) including the obscured representation of atleast the portion of the first user interface of the applicationincludes displaying an obscured representation of the portion of thefirst user interface of the application at a second brightness levelthat is lower than the first brightness level (e.g., as shown in FIGS.18C, 18D, and 18H). In some embodiments, the first user interface isdisplayed at a higher brightness level than the second user interface.Dimming the interface of the application provides the user with visualfeedback that the device is operating in a lower power consumption modewhile still providing the user with feedback about the application thatwas displayed when the device entered the lower power consumption mode.Additionally, dimming the interface of the application provides the userwith additional security, as the contents of the application are lessvisible. Providing improved visual feedback to the user and improvingsecurity enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Additionally, dimmingthe interface of the application reduces the brightness of the display,which reduces power usage and improves the battery life of the device.

In some embodiments, replacing the first user interface (e.g., 1802,1814) with the second user interface (e.g., 1806, 1816) includes dimmingthe display by an amount to reduce the brightness of the display, theamount based on the content of the first user interface (e.g., 1802,1814). In some embodiments, the electronic device dims the displays morewhen the content of the first user interface is brighter (e.g., includesbrighter images) than when the content of the first user interface isless bright (e.g., includes less bright images). In some embodiments,the amount by which the electronic device dims the brightness of thedisplay is based on a requirement to meet a threshold APL when thesecond user interface is displayed. Dimming the interface of theapplication by an amount based on the content of the interface enablesthe device to, for example, dim brighter user interface more and dimless-brighter user interfaces less, thereby achieving a thresholdreduced APL, which reduces power usage and improves the battery life ofthe device.

In some embodiments, replacing the first user interface (e.g., 1802,1814) with the second user interface (e.g., 1806, 1816) includes dimmingthe display by an amount to reduce the brightness of the display, theamount based on an environmental brightness level (e.g., ambient lightlevel). In some embodiments, the amount of dimming increases as theenvironmental brightness increases and the amount of dimming decreasesas the environmental brightness decreases (e.g., based on a magnitude ofchange in the environmental brightness level). In some embodiments, theamount of dimming decreases as the environmental brightness increasesand the amount of dimming increases as the environmental brightnessdecreases (e.g., based on a magnitude of change in the environmentalbrightness level). Dimming the display based on environmental brightnesslevels allows the contents of the display to be more easily visible inbright ambient light environments, thereby providing the user withimproved visual feedback, while reducing battery usage in reducedambient light environments. Providing improved visual feedback to theuser enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice). Reducing the display brightness reduces power usage andimproves the battery life of the device.

In some embodiments, replacing, on the display, the first user interface(e.g., 1802, 1814) with a second user interface (e.g., 1806, 1816)including the obscured representation of at least a portion of the firstuser interface (e.g., 1802, 1814) of the application includes displayinga first animation of the at least a portion of the first user interfacetransitioning from an unobscured state to the obscured state. In someembodiments, displaying the time indicator (e.g., 1806 b, 1814 f) at theposition on the display overlapping at least a portion of the obscuredrepresentation (e.g., 1802 c, 1814 c) of the at least a portion of thefirst user interface of the application includes displaying a secondanimation of the time indicator becoming displayed (e.g., an animationof the time indicator appearing (e.g., transitioning from being notdisplayed to displayed; moving from a previous position to the finalposition) at the position on the display overlapping at least a portionof the obscured representation of the at least a portion of the firstuser interface of the application). In some embodiments, at least aportion of the first animation occurs concurrently with at least aportion of the second animation. In some embodiments, the firstanimation and the second animation are synchronized (e.g., synchronizedto start at the same time and/or end at the same time). In someembodiments, time indicator displayed in the first user interface fadesout while the time indicator at the position on the display overlappingthe at least portion of the obscured representation of the userinterface of the application fades in. In some embodiments, the timeindicator at the first position fades out and time indicator at theposition on the display overlapping the at least portion of the obscuredrepresentation of the user interface of the application fades in tocause a visual cross-fade transition over time.

In some embodiments, displaying the first user interface (e.g., 1802,1814) includes displaying the time indicator (e.g., 1802 b, 1814 b) at afirst display size and at a first position on the display that isdifferent from the position on the display overlapping the at leastportion of the obscured representation of the application in the secondmode. In some embodiments, displaying the time indicator (e.g., 1806 b,1814 f) at the position on the display overlapping at least a portion ofthe obscured representation of the user interface of the applicationincludes displaying an animation of: the time indicator expanding fromthe first display size (e.g., as in 1802 b, 1814 b) to a second displaysize (e.g., as in 1806 b, 1814 f) that is different from the firstdisplay size, and the time indicator translating from the first positionon the display (e.g., as in 1802 b, 1814 b) to the position on thedisplay (e.g., as in 1806 b, 1814 f) overlapping the at least portion ofthe obscured representation of the application. In some embodiments, thefirst position is adjacent to an edge of the display (e.g., a top edge)and translating to the position on the display overlapping the at leastportion of the obscured representation of the application includestranslating the time indicator away from the edge of the display.

In some embodiments, while the electronic device (e.g., 600) is in thesecond mode and the time indicator (e.g., 1806 b, 1814 f) is displayedat the position on the display overlapping at least portion of theobscured representation of the at least portion of the first userinterface of the application (e.g., time overlay), the electronic device(e.g., 600) detects a first user input (e.g., a wrist raise gesture, atap gesture on a touch-sensitive surface of the displays). In responseto detecting the first user input, the electronic device (e.g., 600)ceases to display the time indicator (e.g., 1806 b, 1814 f) at theposition on the display overlapping at least a portion of the obscuredrepresentation of the at least a portion of the first user interface ofthe application (e.g., ceasing to display the time indicator altogether;displaying the time indicator at another position).

In some embodiments, while the electronic device (e.g., 600) is in thesecond mode and the time indicator (e.g., 1806 b, 1814 f) is displayedat the position on the display overlapping the at least portion of theobscured representation of the at least portion of the first userinterface of the application (e.g., time overlay), the electronic device(e.g., 600) detects a first user input (e.g., a wrist raise gesture, atap gesture on a touch-sensitive surface of the displays). In responseto detecting the first user input, the electronic device (e.g., 600)replaces, on the display, the second user interface (e.g., 1806,1808,1816, a lower power consumption interface) including the obscuredrepresentation of the at least portion of the first user interface ofthe application with the first user interface (e.g., 1812). In someembodiments, in response to detecting the first user input, theelectronic device ceases to obscure the user interface of theapplication.

In some embodiments, the obscured representation (e.g., 1802 a, 1802 cin FIGS. 18C and 18D, 1814 c-1814 e in FIG. 18H) of at least a portionof the first user interface (e.g., 1802, 1814) of the application is astatic representation of the first user interface of the application(e.g., the representation does not update over time). In someembodiments, the second user interface is a snapshot of a user interfaceof the application with the time indicator updating.

In some embodiments, one or more processes for the application are beingprocessed by one or more processors of the electronic device (e.g.,600), while the electronic device (e.g., 600) is operating in the secondmode. In some embodiments, the application is a timer application andone or more processes for the timer application continue to be processedsuch that the timer continues to run and can alert the user when atiming condition is met. In some embodiments, the application is analarm clock application and one or more processes of the alarm clockapplication continue to be processed such that alarm times continue tobe monitored and can alert the user when an alarm condition (e.g., alarmtime is reached) is met.

In some embodiments, while displaying the second user interface (e.g.,1806, 1808, 1816, in the second mode), the electronic device (e.g., 600)detects that the electronic device has met a timeout criteria (e.g., apredetermined duration of time has lapsed since the electronic device isdisplaying the second user interface without receiving a qualifying userinput, such as a wrist raise or a tap input on a touch-sensitivesurface). In response to detecting that the electronic device has metthe timeout criteria, the electronic device (e.g., 600) replaces displayof the second user interface with display of a first watch face userinterface (e.g., as shown in FIG. 14D at 1416 b) that includes a secondtime indicator (while maintaining the electronic device in the secondmode) without displaying the obscured representation of the portion ofthe first user interface of the application. In some embodiments, thefirst watch face user interface is a lower power consumption interfacedisplayed in the second mode (e.g., a lower power consumption mode),such as described with respect to method 700 of FIG. 7 and thecorresponding description and method 900 of FIG. 9 and the corresponddescription. In some embodiments, when the electronic device has not metthe timeout criteria, the electronic device continues to display thesecond user interface without displaying the first watch face userinterface that includes the second time indicator (while maintaining theelectronic device in the second mode). In some embodiments, the secondtime indicator is different from the first time indicator in one or moreof: a size, a location, and/or a color.

In some embodiments, while displaying the first watch face userinterface (e.g., as shown in FIG. 14D at 1416 b) that includes thesecond time indicator in accordance with the determination that thetimeout condition has occurred, the electronic device (e.g., 600)detects a wrist raise gesture. In response to detecting the wrist raisegesture, the electronic device (e.g., 600) replaces display of the firstwatch face user interface (e.g., as shown in FIG. 14B at FIG. 14D at1416 b) that includes the second time indicator with a second watch faceuser interface (e.g., as shown in FIG. 14D at 1416 d) that includes athird time indicator. The second watch face user interface is displayedat a higher brightness level (e.g., average pixel luminance (APL)) thanthe first watch face user interface. In some embodiments, the firstwatch face user interface and the second watch face user interface donot include graphical elements of the application.

In some embodiments, the display, while displaying the first userinterface of (e.g., 1802, 1814, a higher power consumption interface)the application in the first mode, has a first display brightness (e.g.,average pixel luminance (APL), average lumen output, total lumen output,average illuminance, or total illuminance of the indicator on thedisplay; brightness expressed in nits, lux, or lumens) and the display,while displaying the second user interface (e.g., 1806, 1808, 1816, alower power consumption interface) including an obscured representationof at least a portion of the first user interface of the application(e.g., in the second mode), has a second display brightness that islower than the first display brightness.

In some embodiments, the electronic device (e.g., 600) receives (e.g.,via wireless communication) a notification. Subsequent to (e.g., inresponse to receiving) receiving the notification, the electronic device(e.g., 600) displays a first notification user interface (e.g., 1820)corresponding to the notification (e.g., including content received inthe notification). While displaying the first notification userinterface (e.g., 1820) corresponding to the notification, the electronicdevice (e.g., 600) detects a wrist down gesture (detecting that the userhas moved their wrist that is wearing the electronic device from araised position to a non-raised position). In response to detecting thewrist down gesture: the electronic device (e.g., 600) replaces, on thedisplay, the notification user interface (e.g., 1820) with a secondnotification user interface (e.g., a lower power consumption interface)including an obscured representation of at least a portion of the firstnotification user interface (e.g., 1820) corresponding to thenotification (e.g., a representation of the same graphical objectincluding the same data with reduced sharpness (detail) or contrast(e.g., blurred); a representation resulting from applying a non-linearfilter to the representation), and the electronic device (e.g., 600)displays a time indicator at a position on the display overlapping atleast a portion of the obscured representation of the first notificationuser interface (e.g., time overlay). In some embodiments, obscuringincludes blurring, scaling down/reducing in size, and/or dimming.Obscuring a representation of the first notification user interfaceprovides the user with visual feedback that the device is operating in alower power consumption mode while still providing the user withfeedback about the notification user interface that was displayed whenthe device entered the lower power consumption mode. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 1900 (e.g., FIG. 19) are also applicable in an analogous mannerto the methods described above. For example, methods 700, 900, 1100,1300, 1500, and 1700 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1900. For example, the first mode is the same mode throughoutthese methods and the second mode is the same mode throughout thesemethods. For brevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

-   -   As described above, one aspect of the present technology is the        gathering and use of data available from various sources to        improve device user interfaces. The present disclosure        contemplates that in some instances, this gathered data may        include personal information data that uniquely identifies or        can be used to contact or locate a specific person. Such        personal information data can include demographic data,        location-based data, telephone numbers, email addresses, twitter        IDs, home addresses, data or records relating to a user's health        or level of fitness (e.g., vital signs measurements, medication        information, exercise information), date of birth, calendar or        scheduling data, or any other identifying or personal        information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toautomatically display helpful or useful information (e.g., content ofinterest to a user) that may otherwise be cumbersome to access manually.Accordingly, use of such personal information data enables users to haveconvenient access to a wider variety of content. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure. For instance, health and fitness data may beused to provide insights into a user's general wellness, or may be usedas positive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof displaying private data such as calendar data or health-related dataon user interfaces, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In another example, users can select not toprovide private data such as calendar data of health-related data forautomated display (e.g., delivery). In yet another example, users canselect to limit the length of time private data such as calendar data orhealth-related data is maintained or entirely prohibit the developmentof data models or profiles derived from such data mood profile. Inaddition to providing “opt in” and “opt out” options, the presentdisclosure contemplates providing notifications relating to the accessor use of personal information. For instance, a user may be notifiedupon downloading an app that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and displayed to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thedevice, or publicly available information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: while the electronic device is in a firstmode, displaying on the display, a first user interface including: afirst time indicator, displayed at a first brightness level; and a firstgraphical object, displayed at a second brightness level; detecting thatthe electronic device has met criteria for transitioning from the firstmode to a second mode; and in response to detecting that the electronicdevice has met the criteria for transitioning from the first mode to thesecond mode, transitioning the electronic device from the first mode tothe second mode; while the electronic device is in the second mode,displaying on the display, a second user interface including: a secondtime indicator indicating the current time, wherein the second timeindicator includes: a first portion that is displayed at a thirdbrightness level that is lower than the first brightness level, at whichthe first time indicator was previously displayed, by a first amount,wherein the first portion includes an inner portion of the second timeindicator; a second portion that is displayed at a fourth brightnesslevel that is lower than the first brightness level, at which the firsttime indicator was previously displayed, by a second amount that isdifferent from the first amount, wherein the second portion includes anoutlining portion that outlines the inner portion of the second timeindicator; and a second graphical object corresponding to the firstgraphical object, wherein the second graphical object is displayed at afifth brightness level that is lower than the second brightness level,at which the first graphical object was previously displayed, by a thirdamount that is different from the first amount of difference inbrightness between the first brightness level and the third brightnesslevel.
 2. The electronic device of claim 1, wherein a first displaybrightness of the display while displaying the first user interfacewhile the electronic device is in the first mode is more than a seconddisplay brightness of the display while displaying the second userinterface while the electronic device is in the second mode.
 3. Theelectronic device of claim 1, wherein the first graphical object is astationary graphical element and wherein the first time indicator is amoving graphical object wherein the first amount of difference inbrightness is less than the third amount of difference in brightness. 4.The electronic device of claim 1, wherein: the first user interfacedisplayed while the electronic device is in the first mode includes athird graphical object displayed at a sixth brightness level that ishigher than the first brightness level; the second user interfacedisplayed while the electronic device is in the second mode includes afourth graphical object displayed at a seventh brightness level, thefourth graphical object corresponding to the third graphical object; andwherein a difference in brightness between the first brightness leveland the fifth brightness level is less than a difference in brightnessbetween the sixth brightness level and the seventh brightness level. 5.The electronic device of claim 1, the one or more programs furtherincluding instructions for: while displaying the first user interfacewhile the electronic device is in the first mode: detecting a change inenvironmental brightness level; and in response to detecting the changein environmental brightness level, changing the brightness at which thefirst user interface is displayed on the display without transitioningthe electronic device to the second mode.
 6. The electronic device ofclaim 1, wherein transitioning the electronic device from the first modeto the second mode includes removing at least some content from thedisplay.
 7. The electronic device of claim 1, wherein transitioning theelectronic device from the first mode to the second mode includesremoving one or more complications from the display.
 8. The electronicdevice of claim 1, wherein transitioning the electronic device from thefirst mode to the second mode includes removing a first set of contentof one or more complications from the display.
 9. The electronic deviceof claim 1, wherein transitioning the electronic device from the firstmode to the second mode includes removing at least a portion of abackground from the display.
 10. The electronic device of claim 1,wherein transitioning the electronic device from the first mode to thesecond mode includes reducing a precision of displayed information. 11.The electronic device of claim 1, wherein transitioning the electronicdevice from the first mode to the second mode includes removing arespective type of information from the display while continuing todisplay information that is not of the respective type of information.12. The electronic device of claim 1, the one or more programs furtherincluding instructions for: subsequent to detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode: in accordance with a determination that an informationsuppression setting is enabled, removing information of a respectivetype of information while continuing to display information that is notof the respective type of information; and in accordance with adetermination that the information suppression setting is not enabled,continuing to display the information of the respective type ofinformation and the information that is not of the respective type ofinformation.
 13. The electronic device of claim 1, wherein transitioningthe electronic device from the first mode to the second mode includesreducing the display size of one or more visual elements.
 14. Theelectronic device of claim 1, the one or more programs further includinginstructions for: prior to displaying the first user interface,detecting a user input, wherein displaying the first user interface isbased on detecting the user input; and wherein the criteria fortransitioning from the first mode to the second mode includes a firstcriterion, wherein: in accordance with a determination that the userinput is of a first type, the first criterion is met based on a firstamount of time having elapsed; and in accordance with a determinationthat the user input is of a second type, the first criterion is metbased on a second amount of time having elapsed, the second amount oftime being different from the first amount of time.
 15. The electronicdevice of claim 1, the one or more programs further includinginstructions for: while in the second mode, detecting a second userinput; and in response to detecting the second user input, transitioningfrom the second mode to the first mode, including replacing display ofthe second user interface with display of the first user interface. 16.The electronic device of claim 15, wherein: the electronic deviceincludes a rotatable input mechanism; the second user input is rotationof the rotatable input mechanism; and replacing display of the seconduser interface with display of the first user interface occurs inconjunction with detecting rotation of the rotatable input mechanism.17. The electronic device of claim 1, wherein the electronic deviceincludes a rotatable input mechanism, and wherein the one or moreprograms further include instructions for: while in the second mode,detecting a third user input; and in response to detecting the thirduser input, transitioning from the second mode to the first mode andincreasing the brightness of the display.
 18. The electronic device ofclaim 1, wherein the first time indicator includes a gradient thatindicates a measure of time and wherein the second time indicator doesnot include a gradient that indicates the measure of time.
 19. Theelectronic device of claim 1, wherein the electronic device includes atouch-sensitive surface, and wherein the one or more programs furtherinclude instructions for: detecting, using the touch-sensitive surface,a tap input at a location corresponding to a displayed complicationassociated with an application; and in response to detecting the tapinput: in accordance with a determination that the electronic device isin the first mode, replacing display of the first time indicator withdisplay of the application; and in accordance with a determination thatthe electronic device is in the second mode, transitioning from thesecond mode to the first mode without replacing display of the secondtime indicator with display of the application.
 20. The electronicdevice of claim 1, the one or more programs further includinginstructions for: detecting a swipe gesture input; and in response todetecting the swipe gesture input: in accordance with a determinationthat the electronic device is in the first mode, performing anoperation; and in accordance with a determination that the electronicdevice is in the second mode, maintaining the electronic device in thesecond mode without performing the operation.
 21. The electronic deviceof claim 1, wherein: the first user interface includes: a firststationary graphical element displayed at a sixth brightness level; anda first non-stationary graphical element displayed at a seventhbrightness level; the second user interface includes: a secondstationary graphical element corresponding to the first stationarygraphical element, wherein the second stationary graphical element isdisplayed at an eighth brightness level that is lower than the sixthbrightness level, at which the first stationary graphical element waspreviously displayed, by a fourth amount; and a second non-stationarygraphical element corresponding to the first non-stationary graphicalelement, wherein the second non-stationary graphical element isdisplayed at a ninth brightness level that is lower than the seventhbrightness level, at which the first non-stationary graphical elementwas previously displayed, by a fifth amount that is less than the fourthamount; and the second user interface, including the second stationaryelement at the eighth brightness level and the second non-stationaryelement at the ninth brightness level, is displayed on the display aftera transition from the first mode to the second mode has concluded. 22.The electronic device of claim 1, wherein the second user interface,including the first portion of the second time indicator at the thirdbrightness level, the second portion of the second time indicator at thefourth brightness level, and the second graphical object at the fifthbrightness level, is displayed on the display after a transition fromthe first mode to the second mode has concluded.
 23. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay, the one or more programs including instructions for: while theelectronic device is in a first mode, displaying on the display, a firstuser interface including: a first time indicator, displayed at a firstbrightness level; and a first graphical object, displayed at a secondbrightness level; detecting that the electronic device has met criteriafor transitioning from the first mode to a second mode; and in responseto detecting that the electronic device has met the criteria fortransitioning from the first mode to the second mode, transitioning theelectronic device from the first mode to the second mode; while theelectronic device is in the second mode, displaying on the display, asecond user interface including: a second time indicator indicating thecurrent time, wherein the second time indicator includes: a firstportion that is displayed at a third brightness level that is lower thanthe first brightness level, at which the first time indicator waspreviously displayed, by a first amount, wherein the first portionincludes an inner portion of the second time indicator; a second portionthat is displayed at a fourth brightness level that is lower than thefirst brightness level, at which the first time indicator was previouslydisplayed, by a second amount that is different from the first amount,wherein the second portion includes an outlining portion that outlinesthe inner portion of the second time indicator; and a second graphicalobject corresponding to the first graphical object, wherein the secondgraphical object is displayed at a fifth brightness level that is lowerthan the second brightness level, at which the first graphical objectwas previously displayed, by a third amount that is different from thefirst amount of difference in brightness between the first brightnesslevel and the third brightness level.
 24. The non-transitorycomputer-readable storage medium of claim 23, wherein a first displaybrightness of the display while displaying the first user interfacewhile the electronic device is in the first mode is more than a seconddisplay brightness of the display while displaying the second userinterface while the electronic device is in the second mode.
 25. Thenon-transitory computer-readable storage medium of claim 23, wherein thefirst graphical object is a stationary graphical element and wherein thefirst time indicator is a moving graphical object wherein the firstamount of difference in brightness is less than the third amount ofdifference in brightness.
 26. The non-transitory computer-readablestorage medium of claim 23, wherein: the first user interface displayedwhile the electronic device is in the first mode includes a thirdgraphical object displayed at a sixth brightness level that is higherthan the first brightness level; the second user interface displayedwhile the electronic device is in the second mode includes a fourthgraphical object displayed at a seventh brightness level, the fourthgraphical object corresponding to the third graphical object; andwherein a difference in brightness between the first brightness leveland the fifth brightness level is less than a difference in brightnessbetween the sixth brightness level and the seventh brightness level. 27.The non-transitory computer-readable storage medium of claim 23, the oneor more programs further including instructions for: while displayingthe first user interface while the electronic device is in the firstmode: detecting a change in environmental brightness level; and inresponse to detecting the change in environmental brightness level,changing the brightness at which the first user interface is displayedon the display without transitioning the electronic device to the secondmode.
 28. The non-transitory computer-readable storage medium of claim23, wherein transitioning the electronic device from the first mode tothe second mode includes removing at least some content from thedisplay.
 29. The non-transitory computer-readable storage medium ofclaim 23, wherein transitioning the electronic device from the firstmode to the second mode includes removing one or more complications fromthe display.
 30. The non-transitory computer-readable storage medium ofclaim 23, wherein transitioning the electronic device from the firstmode to the second mode includes removing a first set of content of oneor more complications from the display.
 31. The non-transitorycomputer-readable storage medium of claim 23, wherein transitioning theelectronic device from the first mode to the second mode includesremoving at least a portion of a background from the display.
 32. Thenon-transitory computer-readable storage medium of claim 23, whereintransitioning the electronic device from the first mode to the secondmode includes reducing a precision of displayed information.
 33. Thenon-transitory computer-readable storage medium of claim 23, whereintransitioning the electronic device from the first mode to the secondmode includes removing a respective type of information from the displaywhile continuing to display information that is not of the respectivetype of information.
 34. The non-transitory computer-readable storagemedium of claim 23, the one or more programs further includinginstructions for: subsequent to detecting that the electronic device hasmet criteria for transitioning from the first mode to a second mode: inaccordance with a determination that an information suppression settingis enabled, removing information of a respective type of informationwhile continuing to display information that is not of the respectivetype of information; and in accordance with a determination that theinformation suppression setting is not enabled, continuing to displaythe information of the respective type of information and theinformation that is not of the respective type of information.
 35. Thenon-transitory computer-readable storage medium of claim 23, whereintransitioning the electronic device from the first mode to the secondmode includes reducing the display size of one or more visual elements.36. The non-transitory computer-readable storage medium of claim 23, theone or more programs further including instructions for: prior todisplaying the first user interface, detecting a user input, whereindisplaying the first user interface is based on detecting the userinput; and wherein the criteria for transitioning from the first mode tothe second mode includes a first criterion, wherein: in accordance witha determination that the user input is of a first type, the firstcriterion is met based on a first amount of time having elapsed; and inaccordance with a determination that the user input is of a second type,the first criterion is met based on a second amount of time havingelapsed, the second amount of time being different from the first amountof time.
 37. The non-transitory computer-readable storage medium ofclaim 23, the one or more programs further including instructions for:while in the second mode, detecting a second user input; and in responseto detecting the second user input, transitioning from the second modeto the first mode, including replacing display of the second userinterface with display of the first user interface.
 38. Thenon-transitory computer-readable storage medium of claim 37, wherein:the electronic device includes a rotatable input mechanism; the seconduser input is rotation of the rotatable input mechanism; and replacingdisplay of the second user interface with display of the first userinterface occurs in conjunction with detecting rotation of the rotatableinput mechanism.
 39. The non-transitory computer-readable storage mediumof claim 23, wherein the electronic device includes a rotatable inputmechanism, and wherein the one or more programs further includeinstructions for: while in the second mode, detecting a third userinput; and in response to detecting the third user input, transitioningfrom the second mode to the first mode and increasing the brightness ofthe display.
 40. The non-transitory computer-readable storage medium ofclaim 23, wherein the first time indicator includes a gradient thatindicates a measure of time and wherein the second time indicator doesnot include a gradient that indicates the measure of time.
 41. Thenon-transitory computer-readable storage medium of claim 23, wherein theelectronic device includes a touch-sensitive surface, and wherein theone or more programs further include instructions for: detecting, usingthe touch-sensitive surface, a tap input at a location corresponding toa displayed complication associated with an application; and in responseto detecting the tap input: in accordance with a determination that theelectronic device is in the first mode, replacing display of the firsttime indicator with display of the application; and in accordance with adetermination that the electronic device is in the second mode,transitioning from the second mode to the first mode without replacingdisplay of the second time indicator with display of the application.42. The non-transitory computer-readable storage medium of claim 23, theone or more programs further including instructions for: detecting aswipe gesture input; and in response to detecting the swipe gestureinput: in accordance with a determination that the electronic device isin the first mode, performing an operation; and in accordance with adetermination that the electronic device is in the second mode,maintaining the electronic device in the second mode without performingthe operation.
 43. The non-transitory computer-readable storage mediumof claim 23, wherein: the first user interface includes: a firststationary graphical element displayed at a sixth brightness level; anda first non-stationary graphical element displayed at a seventhbrightness level; the second user interface includes: a secondstationary graphical element corresponding to the first stationarygraphical element, wherein the second stationary graphical element isdisplayed at an eighth brightness level that is lower than the sixthbrightness level, at which the first stationary graphical element waspreviously displayed, by a fourth amount; and a second non-stationarygraphical element corresponding to the first non-stationary graphicalelement, wherein the second non-stationary graphical element isdisplayed at a ninth brightness level that is lower than the seventhbrightness level, at which the first non-stationary graphical elementwas previously displayed, by a fifth amount that is less than the fourthamount; and the second user interface, including the second stationaryelement at the eighth brightness level and the second non-stationaryelement at the ninth brightness level, is displayed on the display aftera transition from the first mode to the second mode has concluded. 44.The non-transitory computer-readable storage medium of claim 23, whereinthe second user interface, including the first portion of the secondtime indicator at the third brightness level, the second portion of thesecond time indicator at the fourth brightness level, and the secondgraphical object at the fifth brightness level, is displayed on thedisplay after a transition from the first mode to the second mode hasconcluded.
 45. A method, comprising: at an electronic device having adisplay: while the electronic device is in a first mode, displaying onthe display, a first user interface including: a first time indicator,displayed at a first brightness level; and a first graphical object,displayed at a second brightness level; detecting that the electronicdevice has met criteria for transitioning from the first mode to asecond mode; and in response to detecting that the electronic device hasmet the criteria for transitioning from the first mode to the secondmode, transitioning the electronic device from the first mode to thesecond mode; while the electronic device is in the second mode,displaying on the display, a second user interface including: a secondtime indicator indicating the current time, wherein the second timeindicator includes: a first portion that is displayed at a thirdbrightness level that is lower than the first brightness level, at whichthe first time indicator was previously displayed, by a first amount,wherein the first portion includes an inner portion of the second timeindicator; a second portion that is displayed at a fourth brightnesslevel that is lower than the first brightness level, at which the firsttime indicator was previously displayed, by a second amount that isdifferent from the first amount, wherein the second portion includes anoutlining portion that outlines the inner portion of the second timeindicator; and a second graphical object corresponding to the firstgraphical object, wherein the second graphical object is displayed at afourth fifth brightness level that is lower than the second brightnesslevel, at which the first graphical object was previously displayed, bya second third amount that is different from the first amount ofdifference in brightness between the first brightness level and thesecond third brightness level.
 46. The method of claim 45, wherein afirst display brightness of the display while displaying the first userinterface while the electronic device is in the first mode is more thana second display brightness of the display while displaying the seconduser interface while the electronic device is in the second mode. 47.The method of claim 45, wherein the first graphical object is astationary graphical element and wherein the first time indicator is amoving graphical object wherein the first amount of difference inbrightness is less than the third amount of difference in brightness.48. The method of claim 45, wherein: the first user interface displayedwhile the electronic device is in the first mode includes a thirdgraphical object displayed at a sixth brightness level that is higherthan the first brightness level; the second user interface displayedwhile the electronic device is in the second mode includes a fourthgraphical object displayed at a seventh brightness level, the fourthgraphical object corresponding to the third graphical object; andwherein a difference in brightness between the first brightness leveland the fifth brightness level is less than a difference in brightnessbetween the sixth brightness level and the seventh brightness level. 49.The method of claim 45, further comprising: while displaying the firstuser interface while the electronic device is in the first mode:detecting a change in environmental brightness level; and in response todetecting the change in environmental brightness level, changing thebrightness at which the first user interface is displayed on the displaywithout transitioning the electronic device to the second mode.
 50. Themethod of claim 45, wherein transitioning the electronic device from thefirst mode to the second mode includes removing at least some contentfrom the display.
 51. The method of claim 45, wherein transitioning theelectronic device from the first mode to the second mode includesremoving one or more complications from the display.
 52. The method ofclaim 45, wherein transitioning the electronic device from the firstmode to the second mode includes removing a first set of content of oneor more complications from the display.
 53. The method of claim 45,wherein transitioning the electronic device from the first mode to thesecond mode includes removing at least a portion of a background fromthe display.
 54. The method of claim 45, wherein transitioning theelectronic device from the first mode to the second mode includesreducing a precision of displayed information.
 55. The method of claim45, wherein transitioning the electronic device from the first mode tothe second mode includes removing a respective type of information fromthe display while continuing to display information that is not of therespective type of information.
 56. The method of claim 45, furthercomprising: subsequent to detecting that the electronic device has metcriteria for transitioning from the first mode to a second mode: inaccordance with a determination that an information suppression settingis enabled, removing information of a respective type of informationwhile continuing to display information that is not of the respectivetype of information; and in accordance with a determination that theinformation suppression setting is not enabled, continuing to displaythe information of the respective type of information and theinformation that is not of the respective type of information.
 57. Themethod of claim 45, wherein transitioning the electronic device from thefirst mode to the second mode includes reducing the display size of oneor more visual elements.
 58. The method of claim 45, further comprising:prior to displaying the first user interface, detecting a user input,wherein displaying the first user interface is based on detecting theuser input; and wherein the criteria for transitioning from the firstmode to the second mode includes a first criterion, wherein: inaccordance with a determination that the user input is of a first type,the first criterion is met based on a first amount of time havingelapsed; and in accordance with a determination that the user input isof a second type, the first criterion is met based on a second amount oftime having elapsed, the second amount of time being different from thefirst amount of time.
 59. The method of claim 45, further comprising:while in the second mode, detecting a second user input; and in responseto detecting the second user input, transitioning from the second modeto the first mode, including replacing display of the second userinterface with display of the first user interface.
 60. The method ofclaim 59, wherein: the electronic device includes a rotatable inputmechanism; the second user input is rotation of the rotatable inputmechanism; and replacing display of the second user interface withdisplay of the first user interface occurs in conjunction with detectingrotation of the rotatable input mechanism.
 61. The method of claim 45,wherein the electronic device includes a rotatable input mechanism, andwherein the method further comprises: while in the second mode,detecting a third user input; and in response to detecting the thirduser input, transitioning from the second mode to the first mode andincreasing the brightness of the display.
 62. The method of claim 45,wherein the first time indicator includes a gradient that indicates ameasure of time and wherein the second time indicator does not include agradient that indicates the measure of time.
 63. The method of claim 45,wherein the electronic device includes a touch-sensitive surface, andwherein the method further comprises: detecting, using thetouch-sensitive surface, a tap input at a location corresponding to adisplayed complication associated with an application; and in responseto detecting the tap input: in accordance with a determination that theelectronic device is in the first mode, replacing display of the firsttime indicator with display of the application; and in accordance with adetermination that the electronic device is in the second mode,transitioning from the second mode to the first mode without replacingdisplay of the second time indicator with display of the application.64. The method of claim 45, further comprising: detecting a swipegesture input; and in response to detecting the swipe gesture input: inaccordance with a determination that the electronic device is in thefirst mode, performing an operation; and in accordance with adetermination that the electronic device is in the second mode,maintaining the electronic device in the second mode without performingthe operation.
 65. The method of claim 45, wherein: the first userinterface includes: a first stationary graphical element displayed at asixth brightness level; and a first non-stationary graphical elementdisplayed at a seventh brightness level; the second user interfaceincludes: a second stationary graphical element corresponding to thefirst stationary graphical element, wherein the second stationarygraphical element is displayed at an eighth brightness level that islower than the sixth brightness level, at which the first stationarygraphical element was previously displayed, by a fourth amount; and asecond non-stationary graphical element corresponding to the firstnon-stationary graphical element, wherein the second non-stationarygraphical element is displayed at a ninth brightness level that is lowerthan the seventh brightness level, at which the first non-stationarygraphical element was previously displayed, by a fifth amount that isless than the fourth amount; and the second user interface, includingthe second stationary element at the eighth brightness level and thesecond non-stationary element at the ninth brightness level, isdisplayed on the display after a transition from the first mode to thesecond mode has concluded.
 66. The method of claim 45, wherein thesecond user interface, including the first portion of the second timeindicator at the third brightness level, the second portion of thesecond time indicator at the fourth brightness level, and the secondgraphical object at the fifth brightness level, is displayed on thedisplay after a transition from the first mode to the second mode hasconcluded.